This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Implement new `info core mappings' command
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Sergio Durigan Junior <sergiodj at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 9 Nov 2011 21:31:48 +0100
- Subject: Re: [PATCH] Implement new `info core mappings' command
- References: <m3wrbr8olq.fsf@redhat.com> <20111031001117.GA11608@host1.jankratochvil.net> <m3vcr5u9y4.fsf@redhat.com> <20111031070012.GA32610@host1.jankratochvil.net> <m3r51prn6g.fsf@redhat.com> <20111104162648.GA30571@host1.jankratochvil.net> <m3k47bpent.fsf@redhat.com>
On Tue, 08 Nov 2011 02:48:54 +0100, Sergio Durigan Junior wrote:
> > On Thu, 03 Nov 2011 21:00:39 +0100, Sergio Durigan Junior wrote:
> > For ELF core files you should rather check also the ELF segments in
> > objfiles->obfd and verify it is fully covered.
[...]
> This one is giving me headaches...
I have discovered (a bit late) ABRT already supports dumping /proc/PID/maps
along the core file for a dying process (at least on Fedora 16), together with
many other useful information. While I heard Solaris puts some such info
_into_ the core file I find OK to put it _along_ the core file - in the whole
crash report.
So I understand in some corner cases without ABRT `info core mappings' may be
useful but I no longer find too much interest in it myself and some
approximate file suggestion may be just good enough there. After all the
whole information about where is which file mapped is just an approximate
suggestion by GDB anyway.
Thanks,
Jan