From: Roland McGrath <roland@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Mark Kettenis <kettenis@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [branch patch] dwarf-frame.c support for .eh_frame_hdr
Date: Tue, 13 May 2003 03:42:00 -0000 [thread overview]
Message-ID: <200305130342.h4D3gmR23808@magilla.sf.frob.com> (raw)
In-Reply-To: Elena Zannoni's message of Monday, 12 May 2003 23:32:39 -0400 <16064.26455.650498.812097@localhost.redhat.com>
> Is there a way to tell if there is a table?
Sure, my code does check that (size_of_encoded_value returns 0 in that
case). It's just that if there is no table, I don't think there is
anything else useful to try. AFAIK it's not a practical concern. It's
just something that struck me when I came across it.
> I see that the symfile.c change is a good way to test the code, and to
> verify that the stuff that ends up in the core file makes sense. This
> new add-symbol-file command required to read the symbols info from the
> core file is however a bit of a departure from the standard way core
> files are treated in gdb. It also not entirely clear to a user that
> it would be necessary to issue it.
I never suggested that users do such a thing. I did it myself to test the
dwarf-frame.c changes, and included the symfile.c patch so that other could
demonstrate for themselves that the .eh_frame_hdr decoding in fact works.
(If you catch up with your mailbox, you'll notice that today I posted the
patch I wrote later last night to implicitly do it for all core files.)
Thanks,
Roland
next prev parent reply other threads:[~2003-05-13 3:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 9:47 Roland McGrath
2003-05-13 3:27 ` Elena Zannoni
2003-05-13 3:42 ` Roland McGrath [this message]
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
2003-05-15 22:06 ` [branch patch] dwarf-frame.c support for .eh_frame_hdr Roland McGrath
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=200305130342.h4D3gmR23808@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@gnu.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