Graphical idb error (not find start.s)

[J__S__Park]

I'm using intel fortran 11.1.056 on Ubuntu 9.10

If I compile with -g option and run with idb in graphic mode

it said as follows.

Unable to locate source file "/build/buildd/eglibc-2.10.1/sysdeps/x86_64/elf/start.S"
Do you like to search for it manually?

Is there any solution to solve this problem ?

[Hubert_H_Intel]

Quoting - aeroparkgmail.com

I'm using intel fortran 11.1.056 on Ubuntu 9.10

If I compile with -g option and run with idb in graphic mode

it said as follows.

Unable to locate source file "/build/buildd/eglibc-2.10.1/sysdeps/x86_64/elf/start.S"
Do you like to search for it manually?

Is there any solution to solve this problem ?

I could reproduce this bahavior on one of my machines (however previous Ubuntu 9.04). It looks like a bug and I'm going to enter a defect. Could you please check the following: Is your menu 'Run-> Stop' active and when hitting on 'Stop' nothing happens? Is your debuggee running (yellow sign on the buttom message line).
Regards,
Hubert.

[J__S__Park]

Quoting - Hubert Haberstock (Intel)

I could reproduce this bahavior on one of my machines (however previous Ubuntu 9.04). It looks like a bug and I'm going to enter a defect. Could you please check the following: Is your menu 'Run-> Stop' active and when hitting on 'Stop' nothing happens? Is your debuggee running (yellow sign on the buttom message line).
Regards,
Hubert.

After I click 'no' for asking 'start.s', 'Run->Stop' is active and debuggee is running.
Moreover, I can debug my program by manually opening my source files (using File-> Open source files), but it is incovenient.
If it is a bug, I would appreciate to solve this problem as soon as possible.
Thank you for the prompt answer.
Jinseok.

[Hubert_H_Intel]

Quoting - aeroparkgmail.com

After I click 'no' for asking 'start.s', 'Run->Stop' is active and debuggee is running.
Moreover, I can debug my program by manually opening my source files (using File-> Open source files), but it is incovenient.
If it is a bug, I would appreciate to solve this problem as soon as possible.
Thank you for the prompt answer.
Jinseok.

Jinseok,
It's a kind of startup bug under Ubuntu (not seen on other distros) and I'm going to file a defect. On the dialogclick 'No' and continue normal debugging.
Regards,
Hubert.

[gmtanco]

Quoting - Hubert Haberstock (Intel)

Jinseok,
It's a kind of startup bug under Ubuntu (not seen on other distros) and I'm going to file a defect. On the dialogclick 'No' and continue normal debugging.
Regards,
Hubert.

Dear All,

I am running Intel Fortran 11.1.064 over Ubuntu 9.10. I have the same problem as reported in
this thread but, additionally,


1) I cannot debug de code. The executable just runs sending output to the shell window used to
trigger idb, but there is no connection whatsoever between it and the opened source code window.

2) I cannot set break-points inside the source. Clicking on the corresponding source line produces
no result at all...

3) None of the "Open file" windows work. For example, if I use "File -> Open executable", the
window opens and I can select the corresponding file, but nothing happens when I click the OK
button. The same applies to "File -> Open source". In fact, I have to launch "idb executable_code"
in order to load the executable and then double click in the source file window to open the source file.

Is there a way to circunvect this problems or a patch for them?

Thank you,

Gustavo

[Hubert_H_Intel]

Quoting - gmtanco

Dear All,

I am running Intel Fortran 11.1.064 over Ubuntu 9.10. I have the same problem as reported in
this thread but, additionally,


1) I cannot debug de code. The executable just runs sending output to the shell window used to
trigger idb, but there is no connection whatsoever between it and the opened source code window.

2) I cannot set break-points inside the source. Clicking on the corresponding source line produces
no result at all...

3) None of the "Open file" windows work. For example, if I use "File -> Open executable", the
window opens and I can select the corresponding file, but nothing happens when I click the OK
button. The same applies to "File -> Open source". In fact, I have to launch "idb executable_code"
in order to load the executable and then double click in the source file window to open the source file.

Is there a way to circunvect this problems or a patch for them?

Thank you,

Gustavo

Gustavo,

Unfortunately, the startup bug still exists in the newest Debugger 11.1.064. The workaround is to just click 'No' when the dialog "Unable to locate source file ...../start.S" occurrs.
The Open Executalbe dialog obviously doesn't workin this version. A workaround is to load the executable in the GUI Console (e.g. (idb) file sample) or to load the file as argument with the debugger (e.g. $ idb sample
Breakpoints however can be set correctly, either via entering breakpoints in the Console (e.g. (idb) b main) or with right-click in the source window.
Did you build the file correctly with debug infousingoption -debug or -g?
Which compiler did you use?
I'm going to file a defect for the Open Executable dialog issue.
Regards,
Hubert.

[gmtanco]

Quoting - Hubert Haberstock (Intel)

Quoting - gmtanco

Hubert.

Gustavo,

Unfortunately, the startup bug still exists in the newest Debugger 11.1.064. The workaround is to just click 'No' when the dialog "Unable to locate source file ...../start.S" occurrs.
The Open Executalbe dialog obviously doesn't workin this version. A workaround is to load the executable in the GUI Console (e.g. (idb) file sample) or to load the file as argument with the debugger (e.g. $ idb sample
Breakpoints however can be set correctly, either via entering breakpoints in the Console (e.g. (idb) b main) or with right-click in the source window.
Did you build the file correctly with debug infousingoption -debug or -g?
Which compiler did you use?
I'm going to file a defect for the Open Executable dialog issue.
Regards,

Dear Hubert,

Thank you for your reply. I completely uninstalled and installed back the compiler and debugger. Now I am able to debug the code perfectly and set break points by clicking on the source file blue dots. It seems that somehow the original installation of the debugger partially failed (?), while the compiler was ok, since I was able to compile and correctly run the corresponding executable files. The problem that remains is that none of the open file windows work: I have to load the executable file from the command line in the shell (idb myexecfile) and the source file by clicking on it in the "Source File" window (View --> Source Fiels --> [double-click-on-file]). In any case, I am up and running. Thanks a lot!

Gustavo

[Hubert_H_Intel]

Quoting - gmtanco

Dear Hubert,

Thank you for your reply. I completely uninstalled and installed back the compiler and debugger. Now I am able to debug the code perfectly and set break points by clicking on the source file blue dots. It seems that somehow the original installation of the debugger partially failed (?), while the compiler was ok, since I was able to compile and correctly run the corresponding executable files. The problem that remains is that none of the open file windows work: I have to load the executable file from the command line in the shell (idb myexecfile) and the source file by clicking on it in the "Source File" window (View --> Source Fiels --> [double-click-on-file]). In any case, I am up and running. Thanks a lot!

Gustavo

Gustavo,
The underlaying issue is that Ubuntu 9.10 is not yet officially supported; so a couple of GUI functions do not yet work. You needto usethe respective commands on the Console until the GUI is fully working.
Any feedback on the debugger would be very appreciated. Please don't hesitate to submit any experience or comments on the debugger. Thanks in advance.
Regards,
Hubert.

[Hubert_H_Intel]

There is a workaround for the Eclipse bug currently occuring under Ubuntu 9.10. The bug doesn't allow to open an executable (via 'File > Open Executable...') or attach to a running process (via'File > Attach To Process...').

Set the environment variable as follows to get the Intel IDBDebugger dialogs working:

$ export GDK_NATIVE_WINDOWS=1

Hubert.