From: Andrew Cagney <ac131313@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>,
Mark Kettenis <kettenis@chello.nl>,
gdb-patches@sources.redhat.com
Subject: Re: [branch patch] core files as symfiles
Date: Thu, 15 May 2003 23:58:00 -0000 [thread overview]
Message-ID: <3EC429A4.1020906@redhat.com> (raw)
In-Reply-To: <200305152219.h4FMJc812037@magilla.sf.frob.com>
>> Did we settle on this being the solution though?
Not as far as I know.
> I think the
>> /proc/PID/auxv approach is a bit cleaner.
Yep. More importantly it solves the general case.
> We're talking about core files, so what you mean is an NT_AUXV note that
> would give the same information that /proc/PID/auxv would give for a live
> process. It remains to see whether the auxv approach will be accepted in
> the kernel.
Perhaphs someone should find out. What's the best mailing list?
> If that is done, then the corelow.c patch will be superfluous.
Right. And I think both GDB and the Linux kernel will be the better for it.
Andrew
next prev parent reply other threads:[~2003-05-15 23:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 9:47 [branch patch] dwarf-frame.c support for .eh_frame_hdr Roland McGrath
2003-05-13 3:27 ` Elena Zannoni
2003-05-13 3:42 ` Roland McGrath
2003-05-15 21:49 ` Mark Kettenis
2003-05-15 22:00 ` Elena Zannoni
2003-05-15 22:19 ` [branch patch] core files as symfiles Roland McGrath
2003-05-15 23:58 ` Andrew Cagney [this message]
2003-05-15 22:06 ` [branch patch] dwarf-frame.c support for .eh_frame_hdr Roland McGrath
2003-05-13 2:59 [branch patch] core files as symfiles Roland McGrath
2003-05-15 21:58 ` Mark Kettenis
2003-05-15 23:29 ` 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=3EC429A4.1020906@redhat.com \
--to=ac131313@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
--cc=roland@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