From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-86851-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 14251 invoked by alias); 6 Jan 2012 20:48:34 -0000
Received: (qmail 14241 invoked by uid 22791); 6 Jan 2012 20:48:33 -0000
X-SWARE-Spam-Status: No, hits=-0.7 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_WEB,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout23.012.net.il (HELO mtaout23.012.net.il) (80.179.55.175)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 06 Jan 2012 20:48:20 +0000
Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0LXE00L009OU3300@a-mtaout23.012.net.il> for gdb-patches@sourceware.org; Fri, 06 Jan 2012 22:48:19 +0200 (IST)
Received: from HOME-C4E4A596F7 ([77.126.221.183]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LXE00K719SIP7C0@a-mtaout23.012.net.il>; Fri, 06 Jan 2012 22:48:19 +0200 (IST)
Date: Fri, 06 Jan 2012 20:48:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFC stub-side break conditions 0/5]  General info
In-reply-to: <4F0755A0.9050604@earthlink.net>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <8339bso8yv.fsf@gnu.org>
References: <4F05B9FE.1000500@mentor.com> <831urdp8vb.fsf@gnu.org> <4F0755A0.9050604@earthlink.net>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2012-01/txt/msg00248.txt.bz2

> Date: Fri, 06 Jan 2012 12:12:16 -0800
> From: Stan Shebs <stanshebs@earthlink.net>
> 
> For a uniprocessor, target-side evaluation is likely to be a mixed bag; 
> it will be a win for conditional breakpoints in inner loops, but there 
> is a distinct heisenbug possibility, and it will likely be standard 
> advice to go back to host-side evaluation if the code is racy or 
> generally being erratic.
> 
> For multicore, target-side enables debugging usages that have simply not 
> been possible before, such as a conditional breakpoint on 100 cores.  
> Even if half the cores are being slowed down by evaluating the 
> conditional test, it still beats the traffic jam of GDB reading and 
> writing packets for each core!

Thanks.  It would be nice to have this explanation in the manual.