From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC stub-side break conditions 0/5] General info
Date: Fri, 06 Jan 2012 20:48:00 -0000 [thread overview]
Message-ID: <8339bso8yv.fsf@gnu.org> (raw)
In-Reply-To: <4F0755A0.9050604@earthlink.net>
> 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.
prev parent reply other threads:[~2012-01-06 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 14:56 Luis Machado
2012-01-06 7:53 ` Eli Zaretskii
2012-01-06 9:10 ` Joel Brobecker
2012-01-06 10:49 ` Luis Machado
2012-01-06 20:12 ` Stan Shebs
2012-01-06 20:48 ` Eli Zaretskii [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=8339bso8yv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
/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