can't open file in Insight

can't open file in Insight

[yunlu liu]

Hi,
  I installed insight on Ubuntu9.04. I find I couldn't use the insight
to open *.c files. When I click File->open/source choose a *.c file,
it shows error in sourced command file: undefined command: " ". Try
"help". And the stack trace for error is as follows:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Error in sourced command file:
Undefined command: "".  Try "help".

    while executing
"gdb_cmd "source $file_name""
    (procedure "source_file" line 4)
    invoked from within
"source_file"
    invoked from within
".srcwin0.#srcwin0#srcwin#container#pane0#childsite#con#menubar#m.#srcwin0#srcwin#container#pane0#childsite#con#menubar#m#file
invoke active"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list $w invoke active]"
    (procedure "tk::MenuInvoke" line 50)
    invoked from within
"tk::MenuInvoke
.srcwin0.#srcwin0#srcwin#container#pane0#childsite#con#menubar#m.#srcwin0#srcwin#container#pane0#childsite#con#menubar#m#file
1"
    (command bound to event)errorCode is NONE
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I'm just a beginner of insight. I wonder what the problem is. Looking
forward to replies.Thanks a lot.

--
Best Regards!

Re: can't open file in Insight

[Keith Seitz]

On 11/16/2009 01:08 PM, yunlu liu wrote:
> Hi,
>    I installed insight on Ubuntu9.04. I find I couldn't use the insight
> to open *.c files. When I click File->open/source choose a *.c file,
> it shows error in sourced command file: undefined command: " ".

The "source" is really a gdb script file, not a source file. 
Unfortunately, a feature was never added to Insight to allow the user to 
edit the source search path, so the first time you debug something, 
you'll have to manually enter the directory. Insight will save this into 
its preferences.

Open a console window and type "help dir".

Keith

Re: can't open file in Insight

[yunlu liu]

Hi Keith,
  Thanks a lot for your reply. I wonder how could I manually enter the
directory. I find no place to enter on the insight pannel.And I try to
type"insight  .../filename". It just open the insight without file
loading. I appreciate your help very much.

On Tue, Nov 17, 2009 at 5:24 AM, Keith Seitz <keiths@redhat.com> wrote:
> On 11/16/2009 01:08 PM, yunlu liu wrote:
>>
>> Hi,
>>   I installed insight on Ubuntu9.04. I find I couldn't use the insight
>> to open *.c files. When I click File->open/source choose a *.c file,
>> it shows error in sourced command file: undefined command: " ".
>
> The "source" is really a gdb script file, not a source file. Unfortunately,
> a feature was never added to Insight to allow the user to edit the source
> search path, so the first time you debug something, you'll have to manually
> enter the directory. Insight will save this into its preferences.
>
> Open a console window and type "help dir".
>
> Keith
>



-- 
Best Regards!

Re: can't open file in Insight

[Keith Seitz]

On 11/16/2009 01:45 PM, yunlu liu wrote:
> Hi Keith,
>    Thanks a lot for your reply. I wonder how could I manually enter the
> directory. I find no place to enter on the insight pannel.And I try to
> type"insight  .../filename". It just open the insight without file
> loading. I appreciate your help very much.

Open a console window. There's a button for that in the toolbar (it's 
the monitor with shell prompt). There is also the menu View->Console.

Typing "insight ../filename" will have insight/gdb try to open 
"../filename" as an executable, which is not quite what you want. :-)

Keith

Re: can't open file in Insight

[Keith Seitz]

On 11/16/2009 02:12 PM, yunlu liu wrote:
> Hi Keith,
>    Thanks for your email.I try to just enter the filename in the
> console. It shows "undefined command". I try "help dir" and use the dir
> command. No results are shown.I also have no idea how to display the .c
> file. I wonder if I could read and complile the .c file via
> insight.Looking forward to your reply and thanks a lot for your
> consideration:)

I hate to ask this, but I feel compelled. Are you compiling your 
application with debug info? That's the "-g" option to gcc? [Assuming 
your using gcc, of course.] Insight/gdb should be able to automatically 
locate your source files if you do.

To use the dir command:

If you source file lives in "/this/is/where/it/is/myfile.c", open the 
console window and type:

(gdb) dir /this/is/where/it/is

That's it. Insight will remember this the next time you start. To see 
the change immediately, change the display mode of the source window 
from "SOURCE" to anything (like ASSEMBLY) and then back to "SOURCE". I 
believe that should do it.

Keith

Re: can't open file in Insight

[yunlu liu]

Hi Keith,
  Got it. Thanks for your help and consideration very much.Best wishes~

On Tue, Nov 17, 2009 at 6:16 AM, Keith Seitz <keiths@redhat.com> wrote:
> On 11/16/2009 02:12 PM, yunlu liu wrote:
>>
>> Hi Keith,
>>   Thanks for your email.I try to just enter the filename in the
>> console. It shows "undefined command". I try "help dir" and use the dir
>> command. No results are shown.I also have no idea how to display the .c
>> file. I wonder if I could read and complile the .c file via
>> insight.Looking forward to your reply and thanks a lot for your
>> consideration:)
>
> I hate to ask this, but I feel compelled. Are you compiling your application
> with debug info? That's the "-g" option to gcc? [Assuming your using gcc, of
> course.] Insight/gdb should be able to automatically locate your source
> files if you do.
>
> To use the dir command:
>
> If you source file lives in "/this/is/where/it/is/myfile.c", open the
> console window and type:
>
> (gdb) dir /this/is/where/it/is
>
> That's it. Insight will remember this the next time you start. To see the
> change immediately, change the display mode of the source window from
> "SOURCE" to anything (like ASSEMBLY) and then back to "SOURCE". I believe
> that should do it.
>
> Keith
>



-- 
Best Regards!