insight/323: executable must be colocated with source

insight/323: executable must be colocated with source

[michaelprocop]

>Number:         323
>Category:       insight
>Synopsis:       executable must be colocated with source
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Nov 12 14:03:01 UTC 2007
>Closed-Date:
>Last-Modified:
>Originator:     Mike Procopio
>Release:        Insight 6.6
>Organization:
>Environment:
Debug 4
>Description:
I find that I must have my executable file colocated with the source containing the main entry point; otherwise, the gdb child windows pops up with:
>How-To-Repeat:
>From working directory which contains my 1st source file containing main:

insight <Full path to executable in a different directory> &

Depressed run.
A gdb child windows pops up with:
<path to executable>:  No Match.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:

Re: insight/323: executable must be colocated with source

[kseitz]

Synopsis: executable must be colocated with source

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Thu Feb 21 00:54:11 2008
Responsible-Changed-Why:
    mine
State-Changed-From-To: open->analyzed
State-Changed-By: kseitz
State-Changed-When: Thu Feb 21 00:54:11 2008
State-Changed-Why:
    There is something else going on. The source does NOT need to be co-located with your executable: gdb (and hence insight) will find your source files from the debug info contained in the executable.
    
    If this mechanism isn't working, you might need to open a console window and use gdb's "dir" command to help it find the source files (sorry, insight currently doesn't have an equivalent command). Type "help dir" for more information on the dir command in gdb.
    
    I hate to say this, but I've just tested this with my local installation (CVS HEAD), and I am unable to reproduce your problem following the procedure you've specified.
    
    Have you tried using the "-nx" option to gdb/insight? Perhaps there is some stale information in .gdbtkinit?

http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=323