From: Daniel Jacobowitz <drow@false.org>
To: Aleksandar Ristovski <aristovski@qnx.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] core: use core_pid
Date: Thu, 10 Apr 2008 15:16:00 -0000 [thread overview]
Message-ID: <20080410140220.GA21662@caradoc.them.org> (raw)
In-Reply-To: <47C46E0F.2040309@qnx.com>
On Tue, Feb 26, 2008 at 02:52:47PM -0500, Aleksandar Ristovski wrote:
> Daniel Jacobowitz wrote:
>> On Tue, Feb 26, 2008 at 02:37:58PM -0500, Aleksandar Ristovski wrote:
>>> + gdb_assert (abfd != NULL && elf_tdata (abfd) != NULL);
>>
>> What if it's not an ELF core file?
>>
> Didn't think about that (our core can only be ELF).
>
> In that case, do you think something like this would work?
Not quite. I recommend you take a look at bfd/elf.c and
bfd/elf64-x86-64.c to see some different ways ".reg/XXXX" sections are
created. For QNX, you get .reg/TID. But for other targets you get
(LWPID << 16) + PID and core_pid is updated as we go along.
It looks like the information GDB needs doesn't make it out of BFD.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-04-10 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 19:45 Aleksandar Ristovski
2008-02-26 19:53 ` Daniel Jacobowitz
2008-02-26 20:15 ` Aleksandar Ristovski
2008-04-10 15:16 ` Daniel Jacobowitz [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=20080410140220.GA21662@caradoc.them.org \
--to=drow@false.org \
--cc=aristovski@qnx.com \
--cc=gdb-patches@sourceware.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