public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Tim <Tim@deltacompsys.com>
To: Fernando Nasser <fnasser@redhat.com>
Cc: insight@sources.redhat.com
Subject: Re: Source lines out of sync with instructions
Date: Thu, 14 Nov 2002 10:39:00 -0000	[thread overview]
Message-ID: <1037299173.1412.48.camel@TIM.DCS> (raw)
In-Reply-To: <3DD3E9FD.90108@redhat.com>

Sorry, my gdb was compiled as i386-redhat-linux.  Insight was compiled
as i686-pc-linux-gnu.


On Thu, 2002-11-14 at 10:22, Fernando Nasser wrote:
> Can you try and run without the GUI?  If when you say step and get into your 
> subroutine you see the same problem (use the list command to print the source 
> lines or look at what was printed by gdb when it stopped -- usually a line 
> number but you may get an hex address instead/as well).
> 
> Maybe the version of GDB you are using has a problem with your architecture 
> (insight is just a GUI to the GNU debugger, which still does the actual 
> breakpoint debugging).  Is this i386, MIPS, or what?
> 
> Regards,
> Fernando
> 
> 
> Tim wrote:> Thanx! tried -O0 with no luck.  Things are still out of sync.  It
> > appears to happen only after I step into a new compilation unit.  That
> > is, in main everything is fine, but when I break or step into the next
> > compilation unit things get messed up.
> > 
> > Any other thoughts?
> > 
> > On Thu, 2002-11-14 at 09:45, Fernando Nasser wrote:
> > 
> >>Tim wrote:> 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!
> >>
> >>Try compiling your program without optimization...
> >>
> 
> 
> -- 
> Fernando Nasser
> Red Hat - Toronto                       E-Mail:  fnasser@redhat.com
> 2323 Yonge Street, Suite #300
> Toronto, Ontario   M4P 2C9
> 
> 


  parent reply	other threads:[~2002-11-14 18:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-14  9:40 Tim
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 [this message]
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=1037299173.1412.48.camel@TIM.DCS \
    --to=tim@deltacompsys.com \
    --cc=fnasser@redhat.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).