This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

SIGBUS in _dl_runtime_resolve


Hi!

I found some weirdness with Glibc on kFreeBSD after updating our patchset to
2.3.1+cvs. Seems like there's a segfault condition in _dl_runtime_resolve:

$ gdb ar ar.core
GNU gdb 2003-06-06-cvs-debian
[...]
Core was generated by `ar'.
Program terminated with signal 10, Bus error.
[...]
(gdb) bt
#0  0x0000d7b4 in strcmp () from /lib/ld.so.1
#1  0x00006e89 in _dl_name_match_p () from /lib/ld.so.1
#2  0x00006e3c in do_lookup_versioned () from /lib/ld.so.1
#3  0x000060c4 in _dl_lookup_versioned_symbol_internal () from /lib/ld.so.1
#4  0x00008cd0 in fixup () from /lib/ld.so.1
#5  0x00008e80 in _dl_runtime_resolve () from /lib/ld.so.1
#6  0x281a10a0 in jump_table.0 () from /usr/lib/debug/libc.so.0.1
(gdb) q

Sounds like ld.so having allocation problems. Any clue on what could be
broken? (or which place to add debug printf's like crazy monkey)

Note I've reproduced the same error without debug libraries. The difference
being only that jump_table.0 was instead _itoa_upper_digits.

Also note this breakage happens _after_ fixing the brk bug (which I mentioned
before) and verifying that brk works properly.

-- 
Robert Millan

"[..] but the delight and pride of Aule is in the deed of making, and in the
thing made, and neither in possession nor in his own mastery; wherefore he
gives and hoards not, and is free from care, passing ever on to some new work."

 -- J.R.R.T., Ainulindale (Silmarillion)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]