Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Gustavo <luis_gustavo@mentor.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Make breakpoint condition detection trace conditional on remote_debug.
Date: Thu, 08 Mar 2012 23:17:00 -0000	[thread overview]
Message-ID: <4F593DEF.2020100@mentor.com> (raw)
In-Reply-To: <1331232142-10562-1-git-send-email-brobecker@adacore.com>

On 03/08/2012 03:42 PM, Joel Brobecker wrote:
> Hello,
>
> I am investigating a problem where a breakpoint with a condition
> no longer stops the program when running the program through gdbserver.
> One of the things I noticed is this message that keeps popping up in
> the gdbserver output:
>
>      % gdbserver :4444 a
>      Process a created; pid = 10100
>      Listening on port 4444
>      Remote debugging from host 127.0.0.1
>      Found breakpoint condition.
>      Found breakpoint condition.
>      Found breakpoint condition.
>
> This looks like a debugging trace that should only be enable if
> requested.
>
> What do you guys think of this patch.  I'm a little under pressure,
> so I didn't test the patch, but I will if it looks correct. I wasn't
> sure whether I should have used debug_threads or remote_debug...
>
> gdb/gdbserver/ChangeLog:
>
>          * server.c (process_point_options): If a conditional expression
>          is found, only print a message if remote_debug is nonzero.
>
> Thanks,


Thanks for the fix, it is the right thing.

Do you have the testcase handy? I can do some digging...

Did the condition go to the target? How did it evaluate?

Luis


  parent reply	other threads:[~2012-03-08 23:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08 18:42 Joel Brobecker
2012-03-08 18:50 ` Pedro Alves
2012-03-08 20:56   ` Joel Brobecker
2012-03-08 22:23     ` Joel Brobecker
2012-03-08 23:17 ` Luis Gustavo [this message]
2012-03-08 23:33   ` Joel Brobecker
2012-03-08 23:40     ` Luis Gustavo
2012-03-08 23:56       ` Joel Brobecker

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=4F593DEF.2020100@mentor.com \
    --to=luis_gustavo@mentor.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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