Update: Actually, calling ksudss from adb did produce a trace file. Unfortunately, adb never returned control to the shadow process and consequently generated a 16gb trace file (only completed because I bounced the database). That was interesting. I was positive hanganalyze dumps were not that big. =)
You are right, hanganalyze dumps are not that big. Actually, when you call ksudss(), it produces systemstate dump. If you want hanganalyze trace, you need to call ksdhng() instead.
-- Egor http://www.oracledba.ru -- //www.freelists.org/webpage/oracle-l