Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: mludvig@suse.cz
Cc: gdb-patches@sources.redhat.com, ac131313@redhat.com, eliz@elta.co.il
Subject: Re: [RFA/i386newframe] info cfi command
Date: Sat, 31 May 2003 16:35:00 -0000	[thread overview]
Message-ID: <200305311635.h4VGZ2hO005709@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <3ED74F9A.4000309@suse.cz> (message from Michal Ludvig on Fri, 30 May 2003 14:33:30 +0200)

   Date: Fri, 30 May 2003 14:33:30 +0200
   From: Michal Ludvig <mludvig@suse.cz>

   Mark Kettenis told me that:
   > From: Michal Ludvig <mludvig@suse.cz>
   > this patch adds 'info cfi' command which is to be used for examining 
   > debug info. For now it only prints the instructions in a hex-form, but 
   > I'll make a resolver to nice strings later.
   > 
   > Hmm, I wonder whether that should be a maintenance command instead:
   >    'maintenance print cfi'
   > or even
   >    'maintenance print dwarf cfi'
   > or something like that.

   I named it "maint print dwarf2-cfi" - is that OK?

As per Andrew's maint info frame/maint print frame post, "main info
dwarf2-cfi" would be more appropriate.

   The attached version already resolves the data to verbose instructions 
   like DW_CFA_nop. Documentation is also there.

   Can I commit it?

Hmm, I'd prefer that all exported functions from dwarf-frame.c are
prefixed with dwarf2_frame_.

Could you sit on it for a while until I've finished moving over
dwarf-frame.c to mainline?

Mark


  reply	other threads:[~2003-05-31 16:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-29 13:46 Michal Ludvig
2003-05-29 14:16 ` Eli Zaretskii
2003-05-29 14:56   ` Michal Ludvig
2003-05-29 16:29 ` Mark Kettenis
2003-05-29 18:14   ` Andrew Cagney
2003-05-30 12:33   ` Michal Ludvig
2003-05-31 16:35     ` Mark Kettenis [this message]
2003-05-31 16:47       ` Andrew Cagney
2003-05-31 16:49       ` Michal Ludvig
2003-06-01 16:24     ` Eli Zaretskii
2003-06-03  0:39 ` Michael Snyder

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=200305311635.h4VGZ2hO005709@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=ac131313@redhat.com \
    --cc=eliz@elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mludvig@suse.cz \
    /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