From: Tom Tromey <tromey@redhat.com>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Remove same-pc breakpoint notification for internal BPs
Date: Wed, 20 Apr 2011 19:03:00 -0000 [thread overview]
Message-ID: <m3ei4w21ay.fsf@fleche.redhat.com> (raw)
In-Reply-To: <BANLkTim4J5Nnt_bKQvcvHh+ve+jtQdkw8w@mail.gmail.com> (Kevin Pouget's message of "Wed, 20 Apr 2011 09:43:44 -0400")
>>>>> "Kevin" == Kevin Pouget <kevin.pouget@gmail.com> writes:
Kevin> I'd like to suggest a patch which removes the message
>> (gdb) break function
>> Note: breakpoint -1 also set at pc 0x3cbd80e2a0.
>> Breakpoint 1 at 0x3cbd80e2a0
Kevin> when the user sets a breakpoint at the same PC as a _internal_
Kevin> breakpoints.
Seems reasonable to me.
Kevin> (How can I run the testsuite only for gdb.base, for instance? nothing
Kevin> should fail here, because the testsuite only matches "Note: breakpoint
Kevin> \[0-9\]+ also set...", but I would have preferred actually testing
Kevin> it!)
You should usually do full regression tests for a patch. That is, run
before and after, and compare.
You can run just a single directory like:
make check RUNTESTFLAGS=--directory=gdb.base
Kevin> ALL_BREAKPOINTS (b)
Kevin> - others += breakpoint_has_pc (b, pspace, pc, section);
Kevin> + others += breakpoint_has_pc (b, pspace, pc, section)
Kevin> + && b->number >= 0;
You need parens around the RHS here and more indentation on the second
line.
Tom
next prev parent reply other threads:[~2011-04-20 19:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 13:44 Kevin Pouget
2011-04-20 13:57 ` Kevin Pouget
2011-04-20 19:03 ` Tom Tromey [this message]
2011-04-21 8:12 ` Kevin Pouget
2011-04-21 8:49 ` Pedro Alves
2011-04-21 9:25 ` Kevin Pouget
2011-04-21 9:34 ` Kevin Pouget
2011-04-21 14:17 ` Tom Tromey
2011-04-21 14:59 ` Pedro Alves
2011-04-21 15:06 ` Tom Tromey
2011-04-21 15:27 ` Pedro Alves
2011-04-27 13:03 ` Kevin Pouget
2011-08-31 13:18 ` Kevin Pouget
2011-09-05 14:43 ` Pedro Alves
2011-09-15 12:31 ` Kevin Pouget
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=m3ei4w21ay.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevin.pouget@gmail.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