public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb@sources.redhat.com
Subject: Re: dwarf2-frame.c and sym_private
Date: Sun, 22 Jun 2003 21:38:00 -0000	[thread overview]
Message-ID: <20030622213835.GA15031@nevyn.them.org> (raw)
In-Reply-To: <200306222123.h5MLNxQ3018257@elgar.kettenis.dyndns.org>

On Sun, Jun 22, 2003 at 11:23:59PM +0200, Mark Kettenis wrote:
>    Date: Sun, 22 Jun 2003 12:52:35 -0400
>    From: Daniel Jacobowitz <drow@mvista.com>
> 
>    The dwarf2-frame code blithely assumes that objfile->sym_private is
>    always an FDE description.  But nothing stops the file from having
>    non-DWARF-2 debugging information, or no debugging information at
>    all... would you mind if I switched it to use a new dwarf2-specific
>    member of the objfile structure instead?
> 
> I wouldn't mind, although I'm not sure whether adding debug
> format-specific members to the objfile structure is the right
> approach.  Assuming that an object file won't contain unwind info in
> different formats, would adding a member for unwind info to the
> objfile structure be an option.

TBH, I don't think I like the assumption.  It's pretty academic - right
now dwarf2 is the one we support - but we need to be flexible in the
face of really strange input files.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-06-22 21:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-22 16:52 Daniel Jacobowitz
2003-06-22 21:25 ` Mark Kettenis
2003-06-22 21:38   ` Daniel Jacobowitz [this message]
2003-06-22 21:38   ` 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=20030622213835.GA15031@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).