https://bugzilla.novell.com/show_bug.cgi?id=304963
User matz@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=304963#c32
--- Comment #32 from Michael Matz 2008-05-21 08:03:14 MST ---
I wasn't even aware of this bug. Anyway, the initial bug (on 10.2 or 10.3),
that was a race in dlopen leading to the assertion is fixed in glibc.
I think the bug in comment #29 is something different. A Bus error happens
when you e.g. let the CPU run into unmapped memory.
Which would look like an application error (e.g. not correctly checking the
return value of dlsym, or something). The backtrace also doesn't agree with
the ltrace. In the ltrace the BUS error happens after any library call
already returned, i.e. inside application code, so we have inconsistent
data here.
Stanislav: are you sure that you generated the backtrace from the BUS error?
Petr: I assume you can help?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.