From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Forbid watchpoint on a constant value
Date: Wed, 19 May 2010 20:26:00 -0000 [thread overview]
Message-ID: <20100519194322.GA32728@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <201005182043.00433.sergiodj@redhat.com>
On Wed, 19 May 2010 01:42:58 +0200, Sergio Durigan Junior wrote:
> > > --- /dev/null
> > > +++ b/gdb/testsuite/gdb.base/watch-notconst.c
> > > @@ -0,0 +1,23 @@
> > > +/* The original program corresponding to watch-notconst.S.
> > > +
> > > + This program is not compiled; the .S version is used instead.
> > > +
> > > + The purpose of this test is to see if GDB can still watch the
> > > + variable `x' even when we compile the program using -O2
> > > + optimization. */
> >
> > Missing FSF copyleft header.
>
> Thanks.
But now your .S files .debug_line do not correspond to these .c files.
> --- /dev/null
> +++ b/gdb/testsuite/gdb.base/watch-notconst.S
Figured now I see no reason why this file should be precompiled. The only
sensitive testing is in the only function f() in watch-notconst2.S.
watch-notconst.* is just a glue to be able to run f().
> --- /dev/null
> +++ b/gdb/testsuite/gdb.base/watch-notconst2.S
> +.LASF1:
> + .string "watch-notconst2.c"
> +.LASF2:
> + .string "/home/sergio/work/src/git/gdb-src/gdb/testsuite/gdb.base"
I would prefer some adjustment so that gdb and `objdump -dS' works on it.
But this problem may be present even in other testcases, just a nitpick.
Also when it is arch-dependent DWARF it should be IMO in gdb.dwarf2/ (or
possibly gdb.arch/).
Thanks,
Jan
next prev parent reply other threads:[~2010-05-19 19:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 17:36 Sergio Durigan Junior
2010-05-18 17:49 ` Eli Zaretskii
2010-05-18 19:24 ` Sergio Durigan Junior
2010-05-18 23:08 ` Jan Kratochvil
2010-05-18 23:50 ` Sergio Durigan Junior
2010-05-19 20:26 ` Jan Kratochvil [this message]
2010-05-20 6:21 ` Sergio Durigan Junior
2010-05-20 15:50 ` Jan Kratochvil
2010-05-20 16:24 ` Sergio Durigan Junior
2010-05-20 17:03 ` Jan Kratochvil
2010-05-20 17:06 ` Sergio Durigan Junior
2010-05-27 21:54 ` Tom Tromey
2010-05-20 23:23 ` Joel Brobecker
2010-05-20 23:31 ` Sergio Durigan Junior
2010-05-20 23:55 ` Joel Brobecker
2010-05-21 0:09 ` Sergio Durigan Junior
2010-05-21 7:05 ` Eli Zaretskii
2010-05-21 8:44 ` Jan Kratochvil
2010-05-21 21:43 ` Sergio Durigan Junior
2010-05-21 22:20 ` Sergio Durigan Junior
2010-05-29 0:04 ` Joel Brobecker
2010-06-04 13:54 ` Jan Kratochvil
2010-06-04 16:49 ` Tom Tromey
2010-06-05 5:35 ` Sergio Durigan Junior
2010-06-05 14:38 ` Jan Kratochvil
2010-06-06 0:20 ` Sergio Durigan Junior
2010-06-15 17:30 ` Tom Tromey
2010-06-16 18:33 ` Sergio Durigan Junior
2010-06-16 18:36 ` Jan Kratochvil
2010-05-28 5:12 ` Tom Tromey
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=20100519194322.GA32728@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@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