This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: GDB startup session with Eclipse
- From: Vladimir Prus <ghost at cs dot msu dot su>
- To: gdb at sources dot redhat dot com
- Date: Thu, 17 Jan 2008 20:59:24 +0300
- Subject: Re: GDB startup session with Eclipse
- References: <14416165.post@talk.nabble.com> <20071219135523.GA20046@caradoc.them.org> <14418949.post@talk.nabble.com> <20071219153714.GA31218@caradoc.them.org> <14420820.post@talk.nabble.com> <20071219170714.GA4495@caradoc.them.org> <14422110.post@talk.nabble.com> <20071219184050.GA9968@caradoc.them.org> <14915621.post@talk.nabble.com> <14923786.post@talk.nabble.com>
Guillaume MENANT wrote:
>
> By lanching GDB in stand alone and not with Eclipse, GDB stops right after
> it receives the response to the g command. The error displayed is :
>
> Remote debugging using :3000
> 0x40001200 in ?? ()
This is fairly standard response. It says you're connected to
a target, and you're at PC 040001200 and gdb has no idea
what source line or function that is. What's the problem?
>
> Then, target remote stops.
What do you mean "stops"?
> This hex value is the value of the PC sent to GDB. A program is running in
> my board when I launch GDB and this PC value is from my RAM. Why does it
> makes an error ?
I don't see any error message in your email. Did you forget to include one?
- Volodya