Comment 17 for bug 94753

If the non informative stack trace was because of foreign libs, at least the name of the foreign lib should be seen in the stack trace.

Now we have lines like...
#0 0xb7785e09 in vfprintf () from /lib/tls/i686/cmov/libc.so.6

... which is obviously inside of libc, but takes no parameters according to the unwinder. Comparing that to the vfprintf() man page shows that this is wrong.

Or can you point to an example in the stack traces that shows where foreign libraries without debug info is being used?

Note that all the ?? frames are most probably places where the unwinder has already gotten lost and is unwinding garbage.