Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: thorpej@wasabisystems.com
Cc: msnyder@cygnus.com, Eli Zaretskii <eliz@is.elta.co.il>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFC] New command 'gcore'
Date: Thu, 13 Dec 2001 10:50:00 -0000	[thread overview]
Message-ID: <3C18F87F.2070601@cygnus.com> (raw)
In-Reply-To: <20011212180444.M28715@dr-evil.shagadelic.org>

> On Wed, Dec 12, 2001 at 05:48:03PM -0800, Andrew Cagney wrote:
> 
>  > But is that GDB's problem?  If the procfs / ptrace / ttrace interface is 
>  > lieing (returning fp registers for the wrong LWP/thread) then we've 
>  > worse problems than the above :-)
> 
> I suppose it all depends on what interface the backend uses to extract
> the info from the target.


GDB's thread code is implemented as (loosely speaking):

	thread model
	-> thread db library
	-> LWP / linux process / ... interface

VS handling a core file:

	thread model
	-> thread db library
	-> core file interface

provided the core file contains the same information as would have been 
returned by the LWP / linux process / ... interface, it should all be 
fine ......

i think,
Andrew


  reply	other threads:[~2001-12-13 18:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-12 14:17 Michael Snyder
2001-12-12 15:05 ` Eli Zaretskii
2001-12-12 15:29   ` Jason R Thorpe
2001-12-12 17:17     ` Andrew Cagney
2001-12-12 17:35       ` Jason R Thorpe
2001-12-12 17:48         ` Andrew Cagney
2001-12-12 18:06           ` Jason R Thorpe
2001-12-13 10:50             ` Andrew Cagney [this message]
2001-12-12 15:35 ` Kevin Buettner
2001-12-13 11:17   ` Michael Snyder
2001-12-26 12:32   ` Michael Snyder

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=3C18F87F.2070601@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@cygnus.com \
    --cc=thorpej@wasabisystems.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