RE: Source lines out of sync with instructions

[Rod Boyce <rod_boyce at stratexnet dot com>]

More importantly and the first thing you should try before asking question
you should do a make clean and then a make.  I find this problem is 999 out
of a 1000 is caused by dependencies not being compiled correctly after
changes to source code.  This usually means you make file is not working
correctly and cannot determine what has changed in your source.  This
includes everything from clock synchronization to not being able to write a
correct make file I have seen more bad makefiles than good makefiles.  

I would strongly suggest deleting all object files and rebuilding this
should be the first step before asking this kind of question on ANY list.


Regards,
Rod 



 -----Original Message-----
From: 	Fernando Nasser [mailto:fnasser@redhat.com] 
Sent:	Thursday, November 14, 2002 10:23 AM
To:	Tim; insight@sources.redhat.com
Subject:	Re: Source lines out of sync with instructions

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