Summary: | sys-libs/glibc-2.5-r1 - nptl fails an assertion with VMSPLIT_3G | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matteo Sasso <matteo.sasso> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info
kernel .config gdb output |
Description
Matteo Sasso
2007-03-23 23:56:10 UTC
no real information here ... you need to post things like: - `emerge --info` - what version of kopete you're using - build a debug version of kopete and run it through gdb - your kernel .config rebuilding glibc without nptl support is not a useful test Ok, sorry. Kopete is v3.5.6. I'm attaching emerge --info and .config. I'm building the debug version, it'll take some minutes. Created attachment 114213 [details]
emerge --info
Created attachment 114215 [details]
kernel .config
Running kopete under gdb doesn't yield much information. It just prints some (seemingly) unrelated info and then crashes. Even with the crash handler disabled, kopete just quits gracefully and I'm left without a backtrace ("No stack.") Can anyone help me with this? Would it be useful to recompile kdelibs with the debug flag? Thanks for the link, it was somehow helpful and I understood some things about the debugging process which weren't clear before. I applied the suggestions in the howto to both glibc and kopete but I still get the message "Program exited normally." from gdb. I tried to place a breakpoint on __pthread_tpp_change_priority, to no avail: "Function "__pthread_tpp_change_priority" not defined. Make breakpoint pending on future shared library load? (y or [n])" I say "yes", but the break just doesn't happen. I compiled both packages with the debug USE flag, nostrip FEATURE, "-g -ggdb" CFLAGS and CXXFLAGS. Then I run "gdb --args kopete --nocrashhandler". Could you give me some more specific suggestions? It looks like I'm missing something about how gdb works. I'm attaching gdb output. Created attachment 114672 [details]
gdb output
|