From: Mark Kettenis <kettenis@chello.nl>
To: mludvig@suse.cz
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/i386newframe] info cfi command
Date: Thu, 29 May 2003 16:29:00 -0000 [thread overview]
Message-ID: <200305291629.h4TGTLe0000304@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <3ED60F2A.9060108@suse.cz> (message from Michal Ludvig on Thu, 29 May 2003 15:46:18 +0200)
Date: Thu, 29 May 2003 15:46:18 +0200
From: Michal Ludvig <mludvig@suse.cz>
Hi,
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.
Mark
next prev parent reply other threads:[~2003-05-29 16:29 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 [this message]
2003-05-29 18:14 ` Andrew Cagney
2003-05-30 12:33 ` Michal Ludvig
2003-05-31 16:35 ` Mark Kettenis
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=200305291629.h4TGTLe0000304@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--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