From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26073 invoked by alias); 3 Jan 2010 23:44:19 -0000 Received: (qmail 26063 invoked by uid 22791); 3 Jan 2010 23:44:18 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from emailfrontal2.citycable.ch (HELO emailfrontal2.citycable.ch) (85.218.0.121) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Sun, 03 Jan 2010 23:44:13 +0000 Received: from [192.168.0.12] (unknown [85.218.92.99]) (Authenticated sender: guillaume.yziquel@citycable.ch) by emailfrontal2.citycable.ch (Postfix) with ESMTPA id CCC5BB10484; Mon, 4 Jan 2010 00:44:08 +0100 (CET) Message-ID: <4B412BD4.7010203@citycable.ch> Date: Sun, 03 Jan 2010 23:44:00 -0000 From: Guillaume Yziquel Reply-To: guillaume.yziquel@citycable.ch User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090707) MIME-Version: 1.0 To: Jan Kratochvil CC: gdb@sourceware.org Subject: Re: watchpoint hangs. References: <4B3FB2BC.9040104@citycable.ch> <20100102205938.GA9421@host0.dyn.jankratochvil.net> In-Reply-To: <20100102205938.GA9421@host0.dyn.jankratochvil.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-01/txt/msg00036.txt.bz2 Jan Kratochvil a =C3=A9crit : > On Sat, 02 Jan 2010 21:55:24 +0100, Guillaume Yziquel wrote: > >>> (gdb) print box >>> $1 =3D {0x0 } >>> (gdb) watch box >>> Watchpoint 2: box >>> (gdb) continue >>> Continuing. >> >> And it eats up 90% of one of my CPU from now on... >=20 > As it printed "Watchpoint" and not "Hardware watchpoint" it means it had = to > use software watchpoint for some reason. Therefore it needs to singleste= p the > code which should work but it is very very slow. >=20 > 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. >=20 > According to "{0x0 }" your requested memory range is > probably larger. >=20 > Try to reduce the watched memory range in your specific debugging case. >=20 > Regards, > Jan Thank you so much. This has helped tremendously. Symbol collision issue=20 detected and solved. By the way, completely off-topic: moving to git is indeed a very very=20 worthwile solution. It takes quite some pain at the beginning, but it's=20 totally worth it. --=20 Guillaume Yziquel http://yziquel.homelinux.org/