Home » Language IDEs » C / C++ IDE (CDT) » Debugger timeout when launching a debug session
| Debugger timeout when launching a debug session [message #64661] |
Tue, 18 March 2003 13:43  |
Eclipse User |
|
|
|
Hi,
After hacking a plugin.xml file, I have finally managed to get the
CDT/debug launcher to accept that I want to use arm-elf-gdb.exe as the gdb
debugger (for an ARM cpu).
Initially, I got an error message "Don't know how to run. Try 'help
target'"
in the debugger. This problem was solved by writing a small gdb config
file that contains "target sim", thus the ARM simulator is connected in
gdb and it also appears that the CDT debugger does not have any complaints
any longer.
I sometimes can write gdb commands in the debugger console as well,
and gdb is alive and to some extent connected to the CDT debugger GUI,
as arm-elf-gdb.exe writes output in the console view.
The problem is that once I press the "Debug" button to start the debugger,
the debugger is displaying the "Launching local C application" progress
bar and nothing happens before I finally get a (gdb/mi?) timeout. Failure
to
start debugging my "application.elf" in other words.
I have configured the project to use the ELF binary parser, there is an
ELF file to load, the "application.elf" program is pointed out in the
debugger config tab etc. My application is compiled with debug info etc.
What is the debugger doing when I press the "Debug" button? For what
reasons can the CDT debugger result in a timout, when the gdb debugger
seems to work, at least to some extent?
What options do I have to continue debugging this problem, any suggestions
that can help me find a solution and thus allow me to debug ARM *.elf
programs are most welcome!!!
Kind regards,
Johan
|
|
|
| Re: Debugger timeout when launching a debug session [message #64749 is a reply to message #64661] |
Wed, 19 March 2003 08:51  |
| Eclipse User |
|
|
|
This is a multi-part message in MIME format.
--------------020800080507000901040509
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Place this .options file in the directory you start eclipse from then
run eclipse with '-debug', you should then see all the communications between
CDT and gdb in the console. Post the output here, and we may be able to
tell you what's happening.
Dave.
Johan Johansson wrote:
> Hi,
>
> After hacking a plugin.xml file, I have finally managed to get the
> CDT/debug launcher to accept that I want to use arm-elf-gdb.exe as the gdb
> debugger (for an ARM cpu).
>
> Initially, I got an error message "Don't know how to run. Try 'help
> target'"
> in the debugger. This problem was solved by writing a small gdb config
> file that contains "target sim", thus the ARM simulator is connected in
> gdb and it also appears that the CDT debugger does not have any complaints
> any longer.
>
> I sometimes can write gdb commands in the debugger console as well,
> and gdb is alive and to some extent connected to the CDT debugger GUI,
> as arm-elf-gdb.exe writes output in the console view.
>
> The problem is that once I press the "Debug" button to start the debugger,
> the debugger is displaying the "Launching local C application" progress
> bar and nothing happens before I finally get a (gdb/mi?) timeout. Failure
> to
> start debugging my "application.elf" in other words.
>
> I have configured the project to use the ELF binary parser, there is an
> ELF file to load, the "application.elf" program is pointed out in the
> debugger config tab etc. My application is compiled with debug info etc.
>
> What is the debugger doing when I press the "Debug" button? For what
> reasons can the CDT debugger result in a timout, when the gdb debugger
> seems to work, at least to some extent?
>
> What options do I have to continue debugging this problem, any suggestions
> that can help me find a solution and thus allow me to debug ARM *.elf
> programs are most welcome!!!
>
> Kind regards,
> Johan
>
--------------020800080507000901040509
Content-Type: application/x-java-applet;version=1.1.1;
name=".options"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename=".options"
b3JnLmVjbGlwc2UuY2R0LmRlYnVnLm1pLmNvcmUvZGVidWc9dHJ1ZQ==
--------------020800080507000901040509--
|
|
|
| Re: Debugger timeout when launching a debug session [message #64843 is a reply to message #64749] |
Thu, 20 March 2003 13:41 |
| Eclipse User |
|
|
|
Hi,
Thanks for taking the time! I didn't receive any .options file,
so I may have misunderstood you, but I created an ".options" file
and put "target sim" in it to connect arm-elf-gdb.exe to the
arm simulator. Right or wrong on my part?
(I also pointed out another gdb config file that contains "target sim",
otherwise I get a dialog box with the error "Dont know hop to run, try
'help target'" - so the .options file didn't seem to make gdb use the
arm simulator properly)
Anyway, after doing that, I started "eclipse -debug" and got
some output from a console window:
--------------------------------------
Startup: using configuration
file:C:\eclipse\workspace\.metadata\.config\platfor
m.cfg
Boot URL: file:C:/eclipse/plugins/org.eclipse.core.boot_2.1.0/boot.jar
Startup: splash path =
C:\eclipse\plugins\org.eclipse.platform_2.1.0\splash.bmp
Workspace location:
C:\eclipse\workspace
Debug-Options:
file:C:/eclipse/.options
Install URL:
file:C:/eclipse/
---------------------------------
When pressing the "Debug" button to start debugging,
the debugger waits and display the animated progress bar,
but nothing happens, and no gdb related output in the
console windows either, as you can see.
Pls let me know how to proceed. Since I get the "Dont know
how to run, try 'help target' it seems to me gdb is somehow
connected, as this problem is solved then gdb is configured
to startup using a config file that contains "target sim"??????
Any suggestions most appreciated!!!
Kind regards,
Johan
David Inglis wrote:
> This is a multi-part message in MIME format.
> --------------020800080507000901040509
> Content-Type: text/plain; charset=us-ascii; format=flowed
> Content-Transfer-Encoding: 7bit
> Place this .options file in the directory you start eclipse from then
> run eclipse with '-debug', you should then see all the communications between
> CDT and gdb in the console. Post the output here, and we may be able to
> tell you what's happening.
> Dave.
> Johan Johansson wrote:
> > Hi,
> >
> > After hacking a plugin.xml file, I have finally managed to get the
> > CDT/debug launcher to accept that I want to use arm-elf-gdb.exe as the gdb
> > debugger (for an ARM cpu).
> >
> > Initially, I got an error message "Don't know how to run. Try 'help
> > target'"
> > in the debugger. This problem was solved by writing a small gdb config
> > file that contains "target sim", thus the ARM simulator is connected in
> > gdb and it also appears that the CDT debugger does not have any complaints
> > any longer.
> >
> > I sometimes can write gdb commands in the debugger console as well,
> > and gdb is alive and to some extent connected to the CDT debugger GUI,
> > as arm-elf-gdb.exe writes output in the console view.
> >
> > The problem is that once I press the "Debug" button to start the debugger,
> > the debugger is displaying the "Launching local C application" progress
> > bar and nothing happens before I finally get a (gdb/mi?) timeout. Failure
> > to
> > start debugging my "application.elf" in other words.
> >
> > I have configured the project to use the ELF binary parser, there is an
> > ELF file to load, the "application.elf" program is pointed out in the
> > debugger config tab etc. My application is compiled with debug info etc.
> >
> > What is the debugger doing when I press the "Debug" button? For what
> > reasons can the CDT debugger result in a timout, when the gdb debugger
> > seems to work, at least to some extent?
> >
> > What options do I have to continue debugging this problem, any suggestions
> > that can help me find a solution and thus allow me to debug ARM *.elf
> > programs are most welcome!!!
> >
> > Kind regards,
> > Johan
> >
> --------------020800080507000901040509
> Content-Type: application/x-java-applet;version=1.1.1;
> name=".options"
> Content-Transfer-Encoding: base64
> Content-Disposition: inline;
> filename=".options"
> b3JnLmVjbGlwc2UuY2R0LmRlYnVnLm1pLmNvcmUvZGVidWc9dHJ1ZQ==
> --------------020800080507000901040509--
|
|
|
| Re: Debugger timeout when launching a debug session [message #64867 is a reply to message #64749] |
Fri, 21 March 2003 01:12 |
| Eclipse User |
|
|
|
Hi David,
I realised you did include the .options file, I just didn't get it through
the newsgroup web interface. When using a newsreader I got the
file, and re-run the test. Now I get very good debug output, that
gives a lot of information!
Thanks for any suggestions, the log is below!
Pls note I start arm-elf-gdb.exe with a config file that contains
"target sim", that's why the simulator is connected at startup.
Again, thanks for your efforts!
/Johan
==========================
Startup: using configuration
file:C:\eclipse\workspace\.metadata\.config\platfor
m.cfg
Boot URL: file:C:/eclipse/plugins/org.eclipse.core.boot_2.1.0/boot.jar
Startup: splash path =
C:\eclipse\plugins\org.eclipse.platform_2.1.0\splash.bmp
Workspace location:
C:\eclipse\workspace
Debug-Options:
file:C:/eclipse/.options
Install URL:
file:C:/eclipse/
1-gdb-set confirm off
Connected to the simulator.
(gdb)
1^done
2-gdb-set width 0
(gdb)
2^done
3-gdb-set height 0
(gdb)
3^done
(gdb)
4 info remote-process
&"info remote-process\n"
&"Command can only be used when connected to the remote target.\n"
4^error,msg="Command can only be used when connected to the remote target."
(gdb)
5-gdb-set new-console
&"No symbol \"new\" in current context.\n"
5^error,msg="No symbol \"new\" in current context."
(gdb)
6-environment-cd C:\\eclipse\\workspace\\test
6^done
(gdb)
7 info threads
&"info threads\n"
8-break-insert hello.c:7
9-break-insert Init.s:43
10-data-list-register-names
11-break-insert -t main
|
|
|
Goto Forum:
Current Time: Fri Oct 31 05:13:42 EDT 2025
Powered by FUDForum. Page generated in 0.14004 seconds |
Home