Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: Carlo Wood <carlo@alinoe.com>
Cc: Liam Stewart <liams@redhat.com>, gdb@sources.redhat.com
Subject: Re: gdb bugs showing while working on libcwd
Date: Thu, 23 May 2002 18:58:00 -0000	[thread overview]
Message-ID: <20020523205758.A21537@crack.them.org> (raw)
In-Reply-To: <20020524023546.A19030@alinoe.com>; from carlo@alinoe.com on Fri, May 24, 2002 at 02:35:46AM +0200

On Fri, May 24, 2002 at 02:35:46AM +0200, Carlo Wood wrote:
> You now should have a core file.  Here is what I next do
> what reveals a problem with gdb:
> 
> ~/c++/libcwd/testsuite>gdb threads_threads_shared core.21920
> GNU gdb Red Hat Linux (5.1-1)
> Copyright 2001 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 "i386-redhat-linux"...
> 
> warning: core file may not match specified executable file.
> Core was generated by `threads_threads_shared'.
> Program terminated with signal 6, Aborted.
> Reading symbols from /home/carlo/c++/libcwd/.libs/libcwd_r.so.0...done.
> Loaded symbols for /home/carlo/c++/libcwd/.libs/libcwd_r.so.0
> Reading symbols from /lib/libdl.so.2...done.
> Loaded symbols for /lib/libdl.so.2
> Reading symbols from /usr/local/gcc-3.0.4/lib/libstdc++.so.3...done.
> Loaded symbols for /usr/local/gcc-3.0.4/lib/libstdc++.so.3
> Reading symbols from /lib/libm.so.6...done.
> Loaded symbols for /lib/libm.so.6
> Reading symbols from /usr/local/gcc-3.0.4/lib/libgcc_s.so.1...done.
> Loaded symbols for /usr/local/gcc-3.0.4/lib/libgcc_s.so.1
> Reading symbols from /lib/libpthread.so.0...done.
> 
> warning: Unable to set global thread event mask: generic error
> [New Thread 1024 (LWP 21868)]

This specific bug is, however, fixed in GDB 5.2.  It won't help much. 
You are trying to debug a multithreaded application via core dump; only
via my or Mark Gross at Intel's patches does Linux dump enough
information to core files in order to see threads there.  You can find
them in the archives of the linux-kernel list.

-- 
Daniel Jacobowitz                           Debian GNU/Linux Developer
MontaVista Software                         Carnegie Mellon University


  reply	other threads:[~2002-05-24  1:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020522115242.C28512@redhat.com>
     [not found] ` <20020523153816.A4454@alinoe.com>
     [not found]   ` <20020523094527.B25730@redhat.com>
2002-05-23 17:35     ` Carlo Wood
2002-05-23 18:58       ` Daniel Jacobowitz [this message]
2002-05-24  8:41   ` Huge problems with debugging threaded C++ programs Liam Stewart
2002-05-24  9:42     ` gdb bugs showing while working on libcwd Carlo Wood
2002-05-24 18:33       ` Carlo Wood
2002-05-24 18:41         ` Daniel Jacobowitz
2002-05-26 18:43           ` Carlo Wood
2002-05-26 23:03             ` Daniel Jacobowitz
2002-05-27  5:42               ` Carlo Wood
2002-05-27 11:05                 ` Daniel Jacobowitz
2002-05-27 17:01                   ` Carlo Wood
2002-05-28  1:17                     ` Daniel Jacobowitz
2002-05-28  5:50                       ` Carlo Wood
2002-05-28 10:37                         ` Daniel Jacobowitz
2002-05-28 15:54                           ` Carlo Wood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020523205758.A21537@crack.them.org \
    --to=dmj+@andrew.cmu.edu \
    --cc=carlo@alinoe.com \
    --cc=gdb@sources.redhat.com \
    --cc=liams@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox