René Berber wrote:
Pedro Alves wrote:
Corinna Vinschen wrote:
Gdb 6.6 (installed with Insight 6.6) doesn't seem to have the problem:
Unfortunatelly it does. :( If you are seing a different output, it
may be because you built the test app with different -O setting.
-O0 is better for watchp
Pedro Alves wrote:
> Corinna Vinschen wrote:
>
>> I could reproduce it on Win2K SP4, Vista, and under WOW64 on Vista 64.
>
> Thank you.
Gdb 6.6 (installed with Insight 6.6) doesn't seem to have the problem:
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, cov
Corinna Vinschen wrote:
I could reproduce it on Win2K SP4, Vista, and under WOW64 on Vista 64.
Thank you.
Cheers,
Pedro Alves
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/do
On Oct 14 21:12, Pedro Alves wrote:
> René Berber wrote:
>
> (...)
>
>> Program received signal SIGTRAP, Trace/breakpoint trap.
>> main () at main.c:18
>> 18 Sleep (1000);
>> (gdb) p count
>> $3 = 1001
>> (gdb) c
>> Continuing.
>> Hardware watchpoint 2: count
>> Old value = 0
>> New value =
Pedro Alves wrote:
[snip]
> Could you tell me what version of Windows was that?
Windows XP Pro sp2.
[snip]
--
René Berber
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.htm
René Berber wrote:
(...)
Program received signal SIGTRAP, Trace/breakpoint trap.
main () at main.c:18
18Sleep (1000);
(gdb) p count
$3 = 1001
(gdb) c
Continuing.
Hardware watchpoint 2: count
Old value = 0
New value = 1002
(...)
Thanks! That clearly shows the exact same problem.
Pedro Alves wrote:
[snip]
> Any change someone does the little testing to make sure I'm not
> having a local problem here?
>
> as easy as:
>
> gcc main.c -o main.exe -g3 -O0
> gdb main.exe
> start
> watch count
> 'continue' several times, and send me or post here the results.
>
> A log with the
Christopher Faylor escreveu:
On Mon, Oct 08, 2007 at 02:43:31PM +0200, Corinna Vinschen wrote:
On Oct 3 01:47, Pedro Alves wrote:
By a long shot, Cygwin doesn't do anything funny like hooking
GetThreadContext, does it?
cgf might be better suited to answer this, but AFAICS, Cygwin
doesn't hook
On Mon, Oct 08, 2007 at 02:43:31PM +0200, Corinna Vinschen wrote:
>On Oct 3 01:47, Pedro Alves wrote:
>> By a long shot, Cygwin doesn't do anything funny like hooking
>> GetThreadContext, does it?
>
>cgf might be better suited to answer this, but AFAICS, Cygwin
>doesn't hook any system function.
On Oct 3 01:47, Pedro Alves wrote:
> By a long shot, Cygwin doesn't do anything funny like hooking
> GetThreadContext, does it?
cgf might be better suited to answer this, but AFAICS, Cygwin
doesn't hook any system function. It just uses them.
OTOH, there are two calls to SetThreadContext in Cyg
Hi all,
I'm looking over watchpoint support in gdb, and I see something quite
weird here. It seems something/someone is messing with the debug
registers.
When a watchpoint is triggered, the Dr6 register should have a few bits
set to tell the debugger which of the Dr[0-3] watchpoints triggered.
11 matches
Mail list logo
