From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, kettenis@chello.nl
Cc: gdb-patches@sources.redhat.com, nick@nick.uklinux.net
Subject: Re: [PATCH: gdb/mi] -stack-list-locals testcase
Date: Wed, 07 Jan 2004 21:06:00 -0000 [thread overview]
Message-ID: <20040107210659.3EDDE4B35A@berman.michael-chastain.com> (raw)
mark> I think it would be useful if Nick could post the output from "objdump
mark> --stabs" on the generated binary. The output of "gcc -g -S" on the
mark> relevant source file would be even more useful.
Right. Generally, the name and version of the compiler is essential
information here. (The compiler used to build the test program,
not the compiler used to build gdb!)
Michael C
next reply other threads:[~2004-01-07 21:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 21:06 Michael Elizabeth Chastain [this message]
2004-01-07 23:47 ` Nick Roberts
-- strict thread matches above, loose matches on Subject: below --
2004-01-06 1:12 Michael Elizabeth Chastain
2003-11-23 0:16 RFC (gdb/mi): -stack-list-locals Nick Roberts
2003-11-26 0:48 ` Andrew Cagney
2003-12-02 3:14 ` RFC (gdb/mi): -stack-list-locals + PATCH Nick Roberts
2003-12-09 2:42 ` RFC (gdb/mi): -stack-list-locals + REVISED PATCH Nick Roberts
2003-12-10 17:56 ` Andrew Cagney
2003-12-12 20:51 ` RFC (gdb/mi): -stack-list-locals Nick Roberts
2003-12-12 21:09 ` David Carlton
2003-12-17 2:29 ` [PATCH: gdb/mi + doco] -stack-list-locals and -var-list-children Nick Roberts
2004-01-05 21:43 ` Andrew Cagney
2004-01-06 0:14 ` [PATCH: gdb/mi] -stack-list-locals testcase Nick Roberts
2004-01-06 1:07 ` Andrew Cagney
2004-01-07 16:31 ` Andrew Cagney
2004-01-07 17:34 ` Mark Kettenis
2004-01-07 17:40 ` Daniel Jacobowitz
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=20040107210659.3EDDE4B35A@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
--cc=nick@nick.uklinux.net \
/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