public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Michael Snyder <msnyder@redhat.com>,
	Takis Psarogiannakopoulos <takis@XFree86.Org>
Cc: kevinb@redhat.com, gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: GDB 5.1/Core files and ptids (CONT)
Date: Fri, 18 Jan 2002 14:14:00 -0000	[thread overview]
Message-ID: <1020118182344.ZM15107@localhost.localdomain> (raw)
In-Reply-To: Michael Snyder <msnyder@redhat.com> "Re: GDB 5.1/Core files and ptids (CONT)" (Jan 18,  9:11am)

On Jan 18,  9:11am, Michael Snyder wrote:

> Takis Psarogiannakopoulos wrote:

> > Unfortunately it seems that the change of mixed pids to ptids
> > has more problems that I thought in the start of this thread.
> > I am not sure after that change how any OS's that uses corelow.c
> > can debug a multi threaded core file!
> 
> In fact, I think Takis is right.  I noticed while doing the
> gcore work that the thread IDs from multi-threaded corefiles
> on Solaris seemed to be broken, perhaps because corelow 
> has not been made ptid-aware.

Yep, I agree.  As I pointed out to Takis in an earlier message, I think
the right way to fix it is to modify both corelow.c on the GDB side
and elf.c on the bfd side.

My suggestion was that instead of naming sections .reg/PIDLWP where
PIDLWP is a combined (numeric) pid and lwp identifier that these
sections instead be named .reg/PID+LWP where PID is the pid and LWP is
the lwp.

When the LWP doesn't exist or is simply zero, we simply use .reg/PID
as before.  (Or we could use .reg/PID+0.  It doesn't really matter
so long as both sides are in agreement.)

Kevin

      reply	other threads:[~2002-01-18 18:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-18  9:06 Takis Psarogiannakopoulos
2002-01-18  9:41 ` Michael Snyder
2002-01-18 14:14   ` Kevin Buettner [this message]

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=1020118182344.ZM15107@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=msnyder@redhat.com \
    --cc=takis@XFree86.Org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).