Quitting Applications: 0xffff0104 in ?? ()

[kvdman]

I've noticed quite a few legacy BeOS applications run fine on Haiku, but when you quit them, they crash. I've tested a number of applications, and came up with five that crashed when exiting, and was looking to see if there was anything similar between them via the debugger.

Three of the applications have 0xffff0104 in ?? () as #0. They are CrackAttack, GobeProductive, and InDepth. I've included the other two as well.

Perhaps I should file individual tickets?

Attached is a zipfile with the backtraces of the five apps.

[bonefish]

The back traces look very different. Please open separate tickets. The GobeProductive trace might just indicate a problem in the application itself (e.g. double free() or clobbered memory). The 0xffff0104 address is fine -- it is used for syscalls.

Two hints:

• gdb prints a line why a thread entered the debugger (among otherwise useless output). Please also provide it -- in doubt copy all output.
• Please don't attach zipped text files unless there's a good reason (e.g. large test set or something). It just adds overhead for the people who look at the bug report, as they have to download and unzip the stuff first.