Hi again, another reply with a bit more information:
Denis Oliver Kropp wrote: > > (!) [ 1076: 19.429] --> Caught signal 4 (at 0xbe826a2c, illegal > > trap) <-- > > (!) FUSION_PROPERTY_LEASE --> Connection timed out > > (!) [ 1076: 19.521] --> Caught signal 11 (at (nil), invalid > > address) <-- > > Killed > > Do you also have kernel messages regarding this? No, just tons of messages like "Fusion: fusion_ioctl (0x40040403)". > > Unfortunately, using no-vt-switching doesn't help much: we don't > > get that assumption failure above, but the app still receives > > SIGILL (on resume this time), with useless gdb backtrace. > > Please build with "--enable-trace" that maintains a copy of the > call stack and therefore even helps if you have stack corruption. It didn't help, the stack was too corrupted for DFB's code too. We found out that the app produces SIGILL when any signal is sent to it after resume. Furthermore, the vt_thread receives an unexpected signal when suspending: (-) [VT Switcher 187.483] ( 1122) DirectFB/core/layers: suspended. (-) [VT Switcher 187.483] ( 1122) DirectFB/core/screens: suspending... (-) [VT Switcher 187.484] ( 1122) DirectFB/core/screens: suspended. (-) [VT Switcher 187.487] ( 1122) FBDev/VT: ...vt_thread (signal -1) Thanks, Vaclav -- PGP key: 0x465264C9, available from http://pgp.mit.edu/ _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
