From: Andrew STUBBS <andrew.stubbs@st.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 15:29:00 -0000 [thread overview]
Message-ID: <45A50632.8000605@st.com> (raw)
In-Reply-To: <200701101558.33752.bartoschek@or.uni-bonn.de>
Christoph Bartoschek wrote:
> There is no stepping and no breakpoints are active. The program starts, it
> terminates and the debugger is quitted.
In that case GDB is still quietly and automatically monitoring threads
and signals, of which you say there are none, and also the dynamic
linker. I don't know what system you are on or what your program does
but it may be that there is an invisible breakpoint every time a library
is loaded (GDB uses them to load the symbols from the library). I don't
know how that could be affecting anything though. It's possible that a
breakpoint has been set on some data somehow - if you have a symbol with
just the wrong name.
Perhaps you pass in slightly different parameters or environment when
you use GDB. I expect you checked this already.
There's always cache effects of course. Perhaps your program does
something unsafe (self modifying code?) and GDB's influence is just
enough to perturb the results.
Instead of GDB, have you tried running it "under" something else. ptrace
or valgrind perhaps, assuming your on a compatible system.
Well there's some ideas anyway.
Andrew
next prev parent reply other threads:[~2007-01-10 15:29 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
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 [this message]
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=45A50632.8000605@st.com \
--to=andrew.stubbs@st.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