[Bug threads/8963] remote debugging a multithreaded application with gdb creates a SIGTRAP

[Bug threads/8963] remote debugging a multithreaded application with gdb creates a SIGTRAP

[hypothetical25 at gmail dot com]

------- Additional Comments From hypothetical25 at gmail dot com  2009-03-25 06:33 -------
i still see this on ubuntu 8.10. test.c still gives sigtrap when breakpoint is
set on sleeping().

Host:
----

Ubuntu 8.10
$ uname -a
Linux homer-slaver 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686
GNU/Linux

$ arm-linux-gdb --version
GNU gdb 6.4
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i386-pc-linux-gnu
--target=arm-linux-uclibcgnueabi".


$ arm-linux-gcc --version
arm-linux-gcc (GCC) 4.1.1
Copyright (C) 2006 Free Software Foundation, Inc.

Target: arm v5 (gumstix verdex xlp6 running buildroot) (arm-linux-uclibcgnueabi)
-------
[root@gumstix ~]# uname -a
Linux gumstix 2.6.21gum #1 Sun Dec 21 16:37:58 PST 2008 armv5tel unknown



-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=8963

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug threads/8963] remote debugging a multithreaded application with gdb creates a SIGTRAP

[teawater at gmail dot com]

------- Additional Comments From teawater at gmail dot com  2009-03-25 07:13 -------
http://sourceware.org/gdb/wiki/FAQ

GDB does not see any threads besides the one in which crash occurred; or SIGTRAP
kills my program when I set a breakpoint.

    * This frequently happen on Linux, especially on embedded targets. There are
two common causes:
          o

            you are using glibc, and you have stripped libpthread.so.0
          o

            mismatch between libpthread.so.0 and libthread_db.so.1 

      GDB itself does not know how to decode "thread control blocks" maintained
by glibc and considered to be glibc private implementation detail. It uses
libhread_db.so.1 (part of glibc) to help it do so. Therefore, libthread_db.so.1
and libpthread.so.0 must match in version and compilation flags.

      In addition, libthread_db.so.1 requires certain non-global symbols to be
present in libpthread.so.0.

      Solution: use strip --strip-debug libpthread.so.0 instead of strip
libpthread.so.0. 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |WAITING


http://sourceware.org/bugzilla/show_bug.cgi?id=8963

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug threads/8963] remote debugging a multithreaded application with gdb creates a SIGTRAP

[ppluzhnikov at google dot com]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #3439|application/octet-stream    |text/plain
          mime type|                            |


http://sourceware.org/bugzilla/show_bug.cgi?id=8963

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug threads/8963] remote debugging a multithreaded application with gdb creates a SIGTRAP

[max21226 at yahoo dot com]

------- Additional Comments From max21226 at yahoo dot com  2010-02-27 05:49 -------
I'm hitting the same problem.  Anybody knows if this problem is close to be fixed yet?

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=8963

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.