From: Guillaume ORTEGA <guillaume.ortega@open-plug.com>
To: Guillaume ORTEGA <guillaume.ortega@open-plug.com>
Cc: gdb@sourceware.org
Subject: Re: GDB 6.3 : Cannot delete or disable Hardware Watchpoint, Endless loop on Software Watchpoint
Date: Fri, 10 Aug 2007 09:40:00 -0000 [thread overview]
Message-ID: <46BC329B.6030400@open-plug.com> (raw)
In-Reply-To: <46BB3E86.1000207@open-plug.com>
Guillaume ORTEGA wrote:
> Hello,
>
> My system is :
> Windows XP SP2 on an Athlon 64 X2
> GDB 6.3 (Mingw version)
> GCC 4.2.0
>
> 1) When I try to disable or delete an Hardware watchpoint on my
> program (that use some windows dlls without debugging symbols (gtk,
> kernel32, ntdll...)), the program still stop on it.
> When I use the info break command, the watchpoint is disabled or is
> deleted in the list.
>
> 2) Software watchpoints works when I didn't use a dll func (gtk
> function for example), when I use one the program make an infinite loop.
>
> Does a patch or a fix exists for that?
>
> Thanks in Advance,
>
> Guillaume ORTEGA.
>
For the 1), deleted watchpoint cause a SIGTRAP (there is not watchpoint
message).
prev parent reply other threads:[~2007-08-10 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 16:19 Guillaume ORTEGA
2007-08-10 9:40 ` Guillaume ORTEGA [this message]
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=46BC329B.6030400@open-plug.com \
--to=guillaume.ortega@open-plug.com \
--cc=gdb@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