Re: GDB startup session with Eclipse

[Guillaume MENANT <guillaume.menant@geensys.com>]

Ok, I though the line "0x40001200 in ?? ()" was an error :-/

Do you know how to make GDB starts in debug mode in order to see which GDB
command is called by Eclipse.

Thansk.


Vladimir Prus wrote:
> 
> 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
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/GDB-startup-session-with-Eclipse-tp14416165p14947991.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.