Re: source code query

[Keith Seitz <keiths at redhat dot com>]

On 09/09/2009 02:35 AM, pooja nagpal wrote:
> gdb is showing the source code . All the code is complied with "-g"
> option. once I refreshed my PC , insight start picking up the source
> code. but on other machine it is still not picking up the souce code ?

It is unusual for gdb to be able to find the source code and not 
insight. In fact, I'm not sure I've ever seen this before. Try opening a 
debug window and seeing if that says anything when your source file is 
searched. There are two ways to do this:

1) Set GDBTK_DEBUG (optionally also set GDBTK_DEBUGFILENAME). See README.
2) *BEFORE* you encounter the problem (attempt to load the source for 
the file that you think should be found for the first time), open a 
console window and enter "tk ManagedWin::open DebugWin".

And I have to ask, when you say "once I refreshed my PC, insight start 
picking up the source code." What exactly does this mean?

> Second issue -- facing problem with breakpoints also.
> Here we are compiling our source code with GCC complier and debugging
> with cygwin\insight.exe. Is this can be cause of breakpoints .

You haven't told me what your problem with breakpoints is. Can you 
elaborate a little?

> Like gdb we have dir command to set the path . $cdir and $cwd are the
> values of these .

These are simply default values. This may not be sufficient, depending 
on your build environment.

> Do we have some command for the insight also to set the source path.

Unfortunately, no. That was never done. This was part of a big revamp of 
source window loading that I intended to play with, but never got around 
to doing. IMO, this is the biggest "hole" in insight today... Who knows, 
it might just be something that I try to "plug" before the next release.

Insight uses gdb's source search path. To add something to it, simply 
use the console or add something to your .gdbinit file.

Keith