Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: RE: [RFA] Clarify infrun variable naming.
Date: Fri, 23 Nov 2007 15:22:00 -0000	[thread overview]
Message-ID: <fi6qus$a7v$1@ger.gmane.org> (raw)
In-Reply-To: <005c01c82de0$9400be20$bc023a60$@u-strasbg.fr>

Pierre Muller wrote:

> 
> 
>> +   If we hit a breakpoint or watchpoint, and then continue,
>> +   we need to single step the current thread with breakpoints
>> +   disabled, so that to avoid hitting the same breakpoint or
>> +   watchpoint again.  And we should step just a single
>> +   thread and keep other threads stopped, so that
>> +   other threads don't miss breakpoints while they are removed.
>> +
>> +   So, this variable simultaneously means that we need to single
>> +   step current thread, keep other threads stopped, and that
>> +   breakpoints should be removed while we step.
>   But this is the reason of the failure to catch watchpoints
> that happen at the point where we are just stepping over a breakpoint,
> because we step with the watchpoints disabled.
>   Why don't we enable all break- and watchpoints but the
> ones that do have the same PC we are currently?

Because that's extra work, and I haven't got around to that yet ;-)
In case of watchpoints, you probably meant enabling all watchpoint
at different data address, not PC?
 
>   Enabling at least all watchpoints would fix gdb/38 failure as
> seen in gdb.base/watchpoint.exp where it is noted as a KFAIL.
> 
>   I tried to check this by adding a insert_watchpoint function
> a few days ago, but if you are working on it anyhow,
> and probably master this much better than I do, it would be
> great to solve that issue at the same time.

I plan to address this soon (but as a separate patch).

- Volodya



  reply	other threads:[~2007-11-23 15:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-23 13:23 Vladimir Prus
2007-11-23 14:53 ` Pierre Muller
2007-11-23 15:22   ` Vladimir Prus [this message]
2007-11-23 15:41     ` Pierre Muller
2007-11-23 15:51       ` Vladimir Prus
2007-11-23 16:06         ` Daniel Jacobowitz
2007-11-23 17:03           ` Vladimir Prus
2007-11-23 17:27             ` Daniel Jacobowitz
2007-11-23 16:14         ` Pierre Muller
2007-12-05  1:18 ` Jim Blandy
2007-12-05  1:52   ` Daniel Jacobowitz
2007-12-05  2:47     ` Daniel Jacobowitz
2007-12-05  8:37   ` Vladimir Prus
2007-12-05 14:13   ` Vladimir Prus
2007-12-05 21:32     ` Jim Blandy

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='fi6qus$a7v$1@ger.gmane.org' \
    --to=ghost@cs.msu.su \
    --cc=gdb-patches@sources.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