On Sun, Mar 25, 2007 at 12:47:49AM -0000, Johan Walles wrote: > 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.
I think the retrace will not see the foreign lib if it is not available. > > 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. this might be a different issue, e.g. not properly installed libc debug symbols, however the rest of the stack is still worthless. However, I wonder why we have not libvlc.so debug symbols. Anyway, all this discussion is fruitless, as we still have no usable stacktrace. Either producing a stacktrace directly on your system might help, or even better getting a testcase to reproduce. - Alexander -- Firefox crash https://launchpad.net/bugs/94753 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
