From: Mark Kettenis <kettenis@chello.nl>
To: roland@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [branch patch] core files as symfiles
Date: Thu, 15 May 2003 21:58:00 -0000 [thread overview]
Message-ID: <200305152157.h4FLvpNj000488@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <200305130258.h4D2wvY23487@magilla.sf.frob.com> (message from Roland McGrath on Mon, 12 May 2003 19:58:57 -0700)
Date: Mon, 12 May 2003 19:58:57 -0700
From: Roland McGrath <roland@redhat.com>
The following patch causes core files to be implicitly read as symbol files
as well. Using this along with my previous dwarf-frame.c patch vs current
kettenis_i386newframe-20030419-branch gdb, on Linux 2.5.69 on x86 the
backtrace of a thread in a system call from a core dump Just Works.
I've included the trivial symfile.c patch that was in with my dwarf-frame.c
patch again here too, since it's required for the corelow.c patch to work
and these patches work (but cause nothing interesting to happen)
independent of the dwarf-frame.c changes.
The patch looks fine to me, although I'd like to see the opinion of
another GDB developer who's more familiar with this part of the code.
Since this code doesn't depend on any other changes in the
i386newframe branch, perhaps this should go into mainline, and we can
simply merge it into the branch from there. If you think so, please
resubmit this without the reference to "branch" in the subject.
Mark
next prev parent reply other threads:[~2003-05-15 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 2:59 Roland McGrath
2003-05-15 21:58 ` Mark Kettenis [this message]
2003-05-15 23:29 ` Daniel Jacobowitz
2003-05-15 22:00 [branch patch] dwarf-frame.c support for .eh_frame_hdr Elena Zannoni
2003-05-15 22:19 ` [branch patch] core files as symfiles Roland McGrath
2003-05-15 23:58 ` Andrew Cagney
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=200305152157.h4FLvpNj000488@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=gdb-patches@sources.redhat.com \
--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