https://bugzilla.novell.com/show_bug.cgi?id=289641 Cristian Rodriguez changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|pth@novell.com |dmueller@novell.com Component|Development |KDE -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=289641#c2 Richard Guenther changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |ahanssen@trolltech.com --- Comment #2 from Richard Guenther 2007-07-05 02:55:16 MST --- The testcase only compiles for me if I add a declaration for 'mutex'. It also works for me, that is, doesn't look up with or without -fno-exceptions. Can you specify the glibc and kernel versions you are using? Thanks, Richard. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=289641#c4 Michael Matz changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|rguenther@novell.com |matz@novell.com Status|NEEDINFO |ASSIGNED Info Provider|ahanssen@trolltech.com | --- Comment #4 from Michael Matz 2007-07-05 08:50:27 MST --- Oh joy, it's connected with bug 182298 (which in the end was deferred), i.e. the general theme that C++ exception handling and thread cancellation (which you do in your testcase) doesn't go together well in their current state of affairs. The above bug report also leads to http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28145 and http://www.codesourcery.com/archives/c++-pthreads/msg00571.html . It's a very ugly and hard problem to solve as the POSIX and C++ Specs are in conflict :-( I'm not sure why other distribution should not have this very problem, if they're using the same glibc and gcc. Probably it's time to really debug the problem some more as I hinted at in bug 182298 comment #30 onwards . -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=289641 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Commercial |Development -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=289641#c6 Michael Matz changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|matz@novell.com |kernel-maintainers@forge.provo.novell.com Status|ASSIGNED |NEW Component|Development |Kernel Summary|lock-up on Qt app exit from |kernels vDSO mapping broken, leads to pthread |g++ miscompiling pthread |cancel problems. |cleanup code | --- Comment #6 from Michael Matz 2007-07-05 12:05:55 MST --- It's a kernel bug. The problem is, that on i686 the vDSO vsyscall page is used. With address space randomization the vDSO itself won't be mapped to the default address 0xffffe000, but to some other random address. E.g.: b7f10000-b7f11000 r-xp b7f10000 00:00 0 [vdso] That in itself is not yet a problem, but the kernel notifies the process of the wrong address afterwards as can be seen here: % LD_SHOW_AUXV=1 cat /proc/self/maps | egrep 'SYSINFO|vdso' AT_SYSINFO: 0xb7eee400 AT_SYSINFO_EHDR: 0xffffe000 b7eee000-b7eef000 r-xp b7eee000 00:00 0 [vdso] So, the vdso is mapped to 0xb7eee000, and the AT_SYSINFO aux header correctly points inside that DSO. But the ELF Header pointer (AT_SYSINFO_EHDR) remains at 0xffffe000. Now, due to kernel magic the vdso is also mapped at the compat address. But for syscalls the randomized mapping is used (i.e. when following the backtrace you'll somewhen hit a program counter inside the randomized vdso, not inside the 0xffffe000 mapping). The result for all of this is, that dl_iterate_phdr won't find the vDSO because it iterates over the registered ELF headers. Hence if the program counter is inside that DSO (which happens when unwinding through a normal syscall, which is exactly what happens when a thread is canceled which itself is inside a syscall) it can't be associated with any unwind information (the vDSO contains unwind info for itself, but as the vDSO can't be found...). Hence unwinding stops at that point and simply exits the thread. Of course without proper unwinding or running cleanups. kernel-default-2.6.18.2-34 FWIW. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=289641 Dirk Mueller changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=289641#c10 K.R. Foley changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kr@cybsft.com --- Comment #10 from K.R. Foley 2007-09-12 20:53:56 MST --- This looks exactly like the bug I have been chasing for the past couple of days which is documented here http://sourceware.org/bugzilla/show_bug.cgi?id=4123 and showed up when we moved to opensuse 10.2 By the way I get the same behavior whether on 2.6.18.8-0.3-default or 2.6.19-rt6-default (which is a vanilla kernel with realtime patches and a custom patch or two applied). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=289641#c12 --- Comment #12 from K.R. Foley 2007-11-20 09:48:14 MST --- I have some additional info that I have discovered lately. Upgrading to a newer 2.6.23ish kernel resolves this problem for MOST test cases that I have found. Also on 2.6.18 and 2.6.19 kernels this problem can be resolved for MOST test cases by doing "echo 0 > /proc/sys/vm/vdso_enabled". This problem also goes away on OpenSuse 10.3 for MOST test cases. There is one test case that continues to exhibit the problem in all of the above scenarios. I have a test program that is a cobbled-up OpenMotif program that does a pthread_exit. No matter what I try on OpenSuse, with the exception of disabling exceptions, this problem persists. I even tried using lesstif instead of openmotif, but no joy. The only thing I haven't tried is replacing glibc and I would rather not have to go that route if I can avoid it. It is worth noting that this problem doesn't seem to happen at all on Fedora 6 or 7. It is also worth noting that on Fedora they use lesstif instead of openmotif. If there is anything I can do to help debug this, feel free to ask. Upon request, I can post my openmotif test program (I did add it as an attachment on the glibc bugzilla bug #4123) if that will 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.

https://bugzilla.novell.com/show_bug.cgi?id=289641 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=289641#c14 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com, ak@novell.com --- Comment #14 from Jeff Mahoney 2008-01-04 12:47:17 MST --- Andi, will this patch fix this? http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdif... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=289641 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=289641#c16 --- Comment #16 from Jan Beulich 2008-01-07 09:39:54 MST --- I don't think this large patch is really needed here: Simply replacing VDSO_COMPAT_BASE by VDSO_BASE in the definition of AT_SYSINFO_EHDR should get that entry in sync with AT_SYSINFO again (and since the unwind info in the vDSO is position independent, unwinding should work unless glibc has other requirements on addresses being relocated inside the vDSO, in which case the patch above is needed perhaps in addition to this change). Otoh there may have been a reason (which I don't know about) to keep AT_SYSINFO_EHDR at its old value. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=289641 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=289641 User dmueller@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=289641#c21 --- Comment #21 from Dirk Mueller 2008-04-17 03:19:30 MST --- it doesn't seem reproducible on factory anymore, but would the patch apply there as well? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=289641 User aj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=289641#c23 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|ahanssen@trolltech.com | Resolution| |FIXED --- Comment #23 from Andreas Jaeger 2008-10-23 13:32:05 MDT --- according to comment #22 this is fixed. -- 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.