From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Patch: check for over- and under-flow in decode_locdesc
Date: Fri, 19 Nov 2010 16:37:00 -0000 [thread overview]
Message-ID: <20101119163734.GA24966@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3oc9lb7fd.fsf@fleche.redhat.com>
On Fri, 19 Nov 2010 17:32:38 +0100, Tom Tromey wrote:
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> Jan> I will check in the testcase later and if OK.
>
> I am curious to know how you made this.
> Did you just write it by hand?
Yes, copy+modify dw2-bad-parameter-type.{exp,S}.
Sometimes thinking after writing so many gdb.dwarf2/ testcases it could be more
time effective to write some script generator for it instead.
OTOH the gdb.dwarf2/ testcases are for various special cases of DWARF and even
about invalid DWARF. So which generated parts can be automated? Maybe not many.
Regards,
Jan
next prev parent reply other threads:[~2010-11-19 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 21:24 Tom Tromey
2010-11-19 6:25 ` Jan Kratochvil
2010-11-19 16:32 ` Tom Tromey
2010-11-19 16:37 ` Jan Kratochvil [this message]
2010-11-19 16:34 ` Tom Tromey
2010-11-20 1:53 ` Jan Kratochvil
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=20101119163734.GA24966@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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