From: Guillaume Yziquel <guillaume.yziquel@citycable.ch>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: watchpoint hangs.
Date: Sun, 03 Jan 2010 23:44:00 -0000 [thread overview]
Message-ID: <4B412BD4.7010203@citycable.ch> (raw)
In-Reply-To: <20100102205938.GA9421@host0.dyn.jankratochvil.net>
Jan Kratochvil a écrit :
> On Sat, 02 Jan 2010 21:55:24 +0100, Guillaume Yziquel wrote:
>
>>> (gdb) print box
>>> $1 = {0x0 <repeats 64 times>}
>>> (gdb) watch box
>>> Watchpoint 2: box
>>> (gdb) continue
>>> Continuing.
>>
>> And it eats up 90% of one of my CPU from now on...
>
> As it printed "Watchpoint" and not "Hardware watchpoint" it means it had to
> use software watchpoint for some reason. Therefore it needs to singlestep the
> code which should work but it is very very slow.
>
> On amd64 (x86_64) there are only 4 hardware watch registers with 8 bytes range
> each, that is 32 bytes of maximum hardware-watchable bytes of memory.
>
> According to "{0x0 <repeats 64 times>}" your requested memory range is
> probably larger.
>
> Try to reduce the watched memory range in your specific debugging case.
>
> Regards,
> Jan
Thank you so much. This has helped tremendously. Symbol collision issue
detected and solved.
By the way, completely off-topic: moving to git is indeed a very very
worthwile solution. It takes quite some pain at the beginning, but it's
totally worth it.
--
Guillaume Yziquel
http://yziquel.homelinux.org/
prev parent reply other threads:[~2010-01-03 23:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 20:55 Guillaume Yziquel
2010-01-02 20:59 ` Jan Kratochvil
2010-01-03 23:44 ` Guillaume Yziquel [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=4B412BD4.7010203@citycable.ch \
--to=guillaume.yziquel@citycable.ch \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@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