| CDT + gdb + remote target problem [message #124893] |
Sun, 24 October 2004 12:46  |
Eclipse User |
|
|
|
Hi,
I have the toolchain:
CDT -> arm-elf-gdb -> arm simulator in gdb
working just fine. But when I replace the simulator with a real target,
running Redboot, I have a problem. The toolchain is now:
CDT -> arm-elf-gdb -> Redboot
My debug command file is:
set remotebaud 115200
target remote /dev/com1
load
For some reason that I don't understand, gdb seems to think the program is
already running after the load, so when CDT sends "run" gdb replies "Don't
know how to run". In fact, it seems to be well known that in this
situation you need to give gdb the "continue" command rather than "run".
But, of course, CDT always sends "run".
Is there a config option I've missed in Eclipse/CDT? Or in gdb? Someone
out there must be using CDT with remote gdb targets! How do you get this
to work?
Thanks in advance,
--John
|
|
|
| Re: CDT + gdb + remote target problem [message #125442 is a reply to message #124893] |
Fri, 29 October 2004 03:30  |
| Eclipse User |
|
|
|
John Daniels wrote:
> Hi,
> I have the toolchain:
> CDT -> arm-elf-gdb -> arm simulator in gdb
> working just fine. But when I replace the simulator with a real target,
> running Redboot, I have a problem. The toolchain is now:
> CDT -> arm-elf-gdb -> Redboot
> My debug command file is:
> set remotebaud 115200
> target remote /dev/com1
> load
> For some reason that I don't understand, gdb seems to think the program is
> already running after the load, so when CDT sends "run" gdb replies "Don't
> know how to run". In fact, it seems to be well known that in this
> situation you need to give gdb the "continue" command rather than "run".
> But, of course, CDT always sends "run".
> Is there a config option I've missed in Eclipse/CDT? Or in gdb? Someone
> out there must be using CDT with remote gdb targets! How do you get this
> to work?
> Thanks in advance,
> --John
Is no one doing remote debugging with CDT?
--John
|
|
|
| Re: CDT + gdb + remote target problem [message #125491 is a reply to message #125442] |
Sat, 30 October 2004 12:20 |
| Eclipse User |
|
|
|
Okay, so this turns out to be a bug in CDT. CDT has some special code to
handle correctly remote targets connected via TCP/IP but not for serial
connections. My colleague Dave Cleal is going to post a bug and the patch
we've come up with.
John Daniels wrote:
> John Daniels wrote:
> > Hi,
> > I have the toolchain:
> > CDT -> arm-elf-gdb -> arm simulator in gdb
> > working just fine. But when I replace the simulator with a real target,
> > running Redboot, I have a problem. The toolchain is now:
> > CDT -> arm-elf-gdb -> Redboot
> > My debug command file is:
> > set remotebaud 115200
> > target remote /dev/com1
> > load
> > For some reason that I don't understand, gdb seems to think the program is
> > already running after the load, so when CDT sends "run" gdb replies "Don't
> > know how to run". In fact, it seems to be well known that in this
> > situation you need to give gdb the "continue" command rather than "run".
> > But, of course, CDT always sends "run".
> > Is there a config option I've missed in Eclipse/CDT? Or in gdb? Someone
> > out there must be using CDT with remote gdb targets! How do you get this
> > to work?
> > Thanks in advance,
> > --John
> Is no one doing remote debugging with CDT?
> --John
|
|
|
| Re: CDT + gdb + remote target problem [message #125991 is a reply to message #125491] |
Thu, 04 November 2004 14:28 |
| Eclipse User |
|
|
|
Originally posted by: alain.nowhere.ca
John Daniels wrote:
> Okay, so this turns out to be a bug in CDT. CDT has some special code to
> handle correctly remote targets connected via TCP/IP but not for serial
> connections. My colleague Dave Cleal is going to post a bug and the patch
> we've come up with.
Great!
If that be of interrest to you 0yving H. as a list of plugins
that work with the CDT for embedded Arm-elf ... sorry
do not the URL, but google should found a match.
> John Daniels wrote:
>> John Daniels wrote:
>> > Hi,
>> > I have the toolchain:
>> > CDT -> arm-elf-gdb -> arm simulator in gdb
>> > working just fine. But when I replace the simulator with a real target,
>> > running Redboot, I have a problem. The toolchain is now:
>> > CDT -> arm-elf-gdb -> Redboot
>> > My debug command file is:
>> > set remotebaud 115200
>> > target remote /dev/com1
>> > load
>> > For some reason that I don't understand, gdb seems to think the program is
>> > already running after the load, so when CDT sends "run" gdb replies "Don't
>> > know how to run". In fact, it seems to be well known that in this
>> > situation you need to give gdb the "continue" command rather than "run".
>> > But, of course, CDT always sends "run".
>> > Is there a config option I've missed in Eclipse/CDT? Or in gdb? Someone
>> > out there must be using CDT with remote gdb targets! How do you get this
>> > to work?
>> > Thanks in advance,
>> > --John
>> Is no one doing remote debugging with CDT?
>> --John
|
|
|
| Re: CDT + gdb + remote target problem [message #126002 is a reply to message #125491] |
Thu, 04 November 2004 14:28 |
| Eclipse User |
|
|
|
Originally posted by: alain.nowhere.ca
John Daniels wrote:
> Okay, so this turns out to be a bug in CDT. CDT has some special code to
> handle correctly remote targets connected via TCP/IP but not for serial
> connections. My colleague Dave Cleal is going to post a bug and the patch
> we've come up with.
Great!
If that be of interrest to you 0yving H. as a list of plugins
that work with the CDT for embedded Arm-elf ... sorry
do not the URL, but google should found a match.
> John Daniels wrote:
>> John Daniels wrote:
>> > Hi,
>> > I have the toolchain:
>> > CDT -> arm-elf-gdb -> arm simulator in gdb
>> > working just fine. But when I replace the simulator with a real target,
>> > running Redboot, I have a problem. The toolchain is now:
>> > CDT -> arm-elf-gdb -> Redboot
>> > My debug command file is:
>> > set remotebaud 115200
>> > target remote /dev/com1
>> > load
>> > For some reason that I don't understand, gdb seems to think the program is
>> > already running after the load, so when CDT sends "run" gdb replies "Don't
>> > know how to run". In fact, it seems to be well known that in this
>> > situation you need to give gdb the "continue" command rather than "run".
>> > But, of course, CDT always sends "run".
>> > Is there a config option I've missed in Eclipse/CDT? Or in gdb? Someone
>> > out there must be using CDT with remote gdb targets! How do you get this
>> > to work?
>> > Thanks in advance,
>> > --John
>> Is no one doing remote debugging with CDT?
>> --John
|
|
|
Powered by
FUDForum. Page generated in 0.04786 seconds
Home