From: Michael Snyder <msnyder@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Don't use thread_db on corefiles
Date: Fri, 14 Dec 2001 15:43:00 -0000 [thread overview]
Message-ID: <3C1A8DA8.F7149496@cygnus.com> (raw)
In-Reply-To: <20011213232239.A20920@nevyn.them.org>
Daniel Jacobowitz wrote:
>
> On Thu, Dec 13, 2001 at 05:26:47PM -0800, Michael Snyder wrote:
> > Daniel Jacobowitz wrote:
> > >
> > > On Thu, Dec 13, 2001 at 06:56:36PM -0500, Daniel Jacobowitz wrote:
> > > > Thread_db, as things stand, does not work on core files. Is preventing
> > > > it from trying, and thus crashing GDB, really such a disruptive
> > > > suggestion?
> > >
> > > OK, that came out a little harsher than I really wanted it. Sorry.
> > >
> > > I'd like to apply this patch and then add an entry to TODO about
> > > how it "should be done". Is that better?
> >
> > I'd really like to be able to look at the problem myself.
> > I have a lot invested in gdb's thread support on Linux, and
> > I don't have any way to reproduce the problem you're trying
> > to work around. Could you provide a multi-threaded corefile
> > with corresponding symbol file for folks to experiment with?
>
> I'll do that. A binary is at:
> http://www.them.org/~drow/mtc.tgz
> (The core file is a 23MB sparse file because of the unmapped user
> stacks. Careful where you unpack it.)
Oops -- Daniel, I think you sent the wrong corefile. The one in
the tarball is only 1.4 megabytes, and was generated by "gdb ./lotsa_um
core".
Probably you ran gdb in the directory and it dropped core, overwriting
the corefile that you meant to send. ;-(
next prev parent reply other threads:[~2001-12-14 23:43 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 8:50 Daniel Jacobowitz
2001-12-13 10:57 ` Andrew Cagney
2001-12-13 11:37 ` Daniel Jacobowitz
2001-12-16 17:58 ` Daniel Jacobowitz
2001-12-16 21:32 ` Kevin Buettner
2001-12-17 8:34 ` Daniel Jacobowitz
2001-12-13 12:26 ` Michael Snyder
2001-12-13 12:31 ` Daniel Jacobowitz
2001-12-13 14:59 ` Michael Snyder
2001-12-13 15:04 ` Daniel Jacobowitz
2001-12-13 15:08 ` Michael Snyder
2001-12-13 15:11 ` Daniel Jacobowitz
2001-12-13 15:37 ` Andrew Cagney
2001-12-13 15:46 ` Daniel Jacobowitz
2001-12-13 17:14 ` Michael Snyder
2001-12-13 20:29 ` Daniel Jacobowitz
2001-12-14 18:12 ` Andrew Cagney
2001-12-14 18:25 ` Daniel Jacobowitz
2001-12-13 15:47 ` Michael Snyder
2001-12-13 15:57 ` Daniel Jacobowitz
2001-12-13 16:06 ` Daniel Jacobowitz
2001-12-13 17:31 ` Michael Snyder
2001-12-13 20:23 ` Daniel Jacobowitz
2001-12-14 15:43 ` Michael Snyder [this message]
2001-12-14 17:14 ` Daniel Jacobowitz
2001-12-17 11:40 ` Michael Snyder
2001-12-17 11:51 ` Daniel Jacobowitz
2001-12-13 17:26 ` Michael Snyder
2001-12-13 20:27 ` Daniel Jacobowitz
2001-12-14 18:31 ` Andrew Cagney
2001-12-14 18:36 ` Andrew Cagney
2001-12-14 18:42 ` Daniel Jacobowitz
2001-12-15 9:16 ` Andrew Cagney
2001-12-16 12:26 ` Daniel Jacobowitz
2001-12-16 13:29 ` Andrew Cagney
2001-12-16 17:02 ` Daniel Jacobowitz
2002-01-03 17:11 ` Michael Snyder
2002-01-04 10:25 ` Daniel Jacobowitz
2002-01-04 14:49 ` Michael Snyder
2002-01-04 17:28 ` Michael Snyder
2002-01-04 17:47 ` Daniel Jacobowitz
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=3C1A8DA8.F7149496@cygnus.com \
--to=msnyder@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.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