public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Tim <Tim@deltacompsys.com>
To: insight@sources.redhat.com
Subject: Source lines out of sync with instructions
Date: Thu, 14 Nov 2002 09:40:00 -0000	[thread overview]
Message-ID: <1037295643.1411.24.camel@TIM.DCS> (raw)

I have seen this with gdb console so I don't think it is a problem with
insight, but perhaps someone can help me.

When I'm debugging the source code lines get out of sync with the actual
instructions.  Why is this and more importantly how do I stop it?

Thanx!



             reply	other threads:[~2002-11-14 17:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-14  9:40 Tim [this message]
2002-11-14  9:45 ` Fernando Nasser
     [not found]   ` <1037297236.1411.31.camel@TIM.DCS>
2002-11-14 10:22     ` Fernando Nasser
2002-11-14 10:37       ` Tim
2002-11-14 10:39       ` Tim
2002-11-14 10:29 Rod Boyce
2002-11-14 10:55 ` Tim
2002-11-14 11:27 ` Tim
2002-11-14 12:08 Rod Boyce

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=1037295643.1411.24.camel@TIM.DCS \
    --to=tim@deltacompsys.com \
    --cc=insight@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).