Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Michael Snyder <msnyder@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Don't use thread_db on corefiles
Date: Sun, 16 Dec 2001 13:29:00 -0000	[thread overview]
Message-ID: <3C1D123E.3000900@cygnus.com> (raw)
In-Reply-To: <20011216152432.A4182@nevyn.them.org>


> This only works if you're debugging on a very similar host to the one
> the core was dumped on.  If you've got, say, a glibc 2.1.3 host and are
> looking at a glibc 2.2.3 core... well, you can provide target libraries
> and make GDB use those, but there's no way to provide a cross
> libthread_db.


Yep.


> Are we really comfortable with that?  This'll probably cause GDB to
> misbehave in arbitrarily unpredictable ways in that circumstance.  And
> we've no way to detect it that I can see.


By misbehave I guess you mean exibit non-deterministic behavour.  Using 
the current source base, either the GDB build is native and thread-db is 
included (and full thread support in core files is available) XOR GDB is 
a cross, thread-db is not included, and full thread support of core 
files is not available.  I think this is pretty deterministic.

As far as I know, these limitations are exactly the same as for GDB and 
shared libraries.  It just so happens that, for shared libraries, things 
are a little (lot) further down the road of getting the technical 
problems fixed.

Andrew


  reply	other threads:[~2001-12-16 21:29 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
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 [this message]
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=3C1D123E.3000900@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@cygnus.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