Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Danny Backx <danny.backx@scarlet.be>
To: gdb <gdb@sourceware.org>
Subject: gdb influencing app behaviour ?
Date: Mon, 14 Mar 2011 20:26:00 -0000	[thread overview]
Message-ID: <1300134373.2002.8.camel@pavilion> (raw)

Hi,

I was trying to debug the interaction between RoadMap and gpsd's client
library recently. 

I believe I've found my problem, but I think gdb influenced application
behaviour in a way I'd like to understand.

The application uses some gtk call which presumably ends up using
select(2) to trigger a function when data can be read from a socket.

The application appears to behave differently when I set a breakpoint in
that function. (The application and the library were both trying to read
from the socket, by setting the breakpoint the other one would always
win the race.)

How can this be explained ? Am I wrong ?

This is on Ubuntu on a regular PC. http://sf.net/projects/roadmap and
http://gpsd.berlios.de .

	Danny
-- 
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info


             reply	other threads:[~2011-03-14 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 20:26 Danny Backx [this message]
2011-03-15  9:10 ` Andreas Schwab
2011-03-15 19:09   ` Danny Backx

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=1300134373.2002.8.camel@pavilion \
    --to=danny.backx@scarlet.be \
    --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