From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18237 invoked by alias); 9 Aug 2012 16:00:17 -0000 Received: (qmail 18138 invoked by uid 22791); 9 Aug 2012 16:00:06 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 09 Aug 2012 15:59:51 +0000 Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0M8H00300WCDMK00@a-mtaout22.012.net.il> for gdb@sourceware.org; Thu, 09 Aug 2012 18:59:06 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0M8H00358WEI72B0@a-mtaout22.012.net.il>; Thu, 09 Aug 2012 18:59:06 +0300 (IDT) Date: Thu, 09 Aug 2012 16:00:00 -0000 From: Eli Zaretskii Subject: Re: Hardware breakpoint limitation issue during the gdb regression test In-reply-to: <20120809104209.GA25622@host2.jankratochvil.net> To: Jan Kratochvil Cc: mark.kettenis@xs4all.nl, flameroc@gmail.com, yao@codesourcery.com, gdb@sourceware.org Reply-to: Eli Zaretskii Message-id: <83sjbwdpkg.fsf@gnu.org> References: <2908402.0pCVQUbaGe@qiyao.dyndns.org> <201208091030.q79AURkU017337@glazunov.sibelius.xs4all.nl> <20120809104209.GA25622@host2.jankratochvil.net> X-IsSubscribed: yes 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: 2012-08/txt/msg00027.txt.bz2 > Date: Thu, 9 Aug 2012 12:42:09 +0200 > From: Jan Kratochvil > Cc: flameroc@gmail.com, yao@codesourcery.com, gdb@sourceware.org > > On Thu, 09 Aug 2012 12:30:27 +0200, Mark Kettenis wrote: > > No, x86 has even less hardware breakpoints (4). But it will fall back > > to using software breakpoints. > > It will not. Right, it cannot do that, because whether a hardware break/watchpoint can or cannot be inserted is only known when we resume the debuggee.