From: Joel Brobecker <brobecker@adacore.com>
To: Christoph Bartoschek <bartoschek@or.uni-bonn.de>
Cc: gdb@sourceware.org
Subject: Re: Differences between program runs with and without gdb
Date: Wed, 10 Jan 2007 14:35:00 -0000 [thread overview]
Message-ID: <20070110143633.GA23012@adacore.com> (raw)
In-Reply-To: <200701101517.20024.bartoschek@or.uni-bonn.de>
> is there a list of things that could be different between to runs of a
> programm once with and once without running it under gdb?
Generally speaking, GDB tries to be as unobstructive as possible.
In practice, although the debugger interferes very little with
the program execution, it's not completely perfect. The part that
GDB might interfere with which comes first to my mind is thread
scheduling and, to a very small degree, program performance.
--
Joel
next prev parent reply other threads:[~2007-01-10 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 14:18 Christoph Bartoschek
2007-01-10 14:35 ` Joel Brobecker [this message]
2007-01-10 14:49 ` Christoph Bartoschek
2007-01-10 14:53 ` Markus Deuling
2007-01-10 14:59 ` Christoph Bartoschek
2007-01-10 14:57 ` Andrew STUBBS
2007-01-10 14:59 ` Christoph Bartoschek
2007-01-10 15:29 ` Andrew STUBBS
2007-01-10 16:21 ` Christoph Bartoschek
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=20070110143633.GA23012@adacore.com \
--to=brobecker@adacore.com \
--cc=bartoschek@or.uni-bonn.de \
--cc=gdb@sourceware.org \
/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