From: Kevin Buettner <kevinb@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>, gdb-patches@sources.redhat.com
Cc: mec@shout.net
Subject: Re: [RFC/WIP] unit test for separate debug info
Date: Fri, 07 Nov 2003 20:39:00 -0000 [thread overview]
Message-ID: <1031107203932.ZM14510@localhost.localdomain> (raw)
In-Reply-To: Elena Zannoni <ezannoni@redhat.com> "[RFC/WIP] unit test for separate debug info" (Nov 7, 3:03pm)
On Nov 7, 3:03pm, Elena Zannoni wrote:
> Anyway, here is what I did. I used the break.exp and break.c files as
> templates. I actually cloned break.exp and added fiddling with the
> separate debug info. Break.exp is usually a decent smoke test for gdb.
> No need to clone break.c.
Prior to cloning, it'd be nice if break.exp could be converted to use
gdb_get_line_number instead of containing explicit references to line
numbers in break.c.
> (BTW, should cloned files retain the original
> copyright years?)
I think so.
Kevin
next prev parent reply other threads:[~2003-11-07 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 20:03 Elena Zannoni
2003-11-07 20:39 ` Kevin Buettner [this message]
2003-11-07 20:21 Michael Elizabeth Chastain
2003-11-08 1:28 Michael Elizabeth Chastain
2003-11-11 16:26 ` Elena Zannoni
2003-11-11 21:19 Michael Elizabeth Chastain
2003-11-11 21:22 ` Daniel Jacobowitz
2003-11-12 14:44 ` Elena Zannoni
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=1031107203932.ZM14510@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.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