RE: qSymbol when using symbol-file

"[email protected]" <[email protected]>
Newsgroups gmane.comp.gdb.devel
Message-ID <4dcec0b82884469cb9dae76f5d8a305c@BY2PR03MB175.namprd03.prod.outlook.com>
Hi,
Just a reminder for the email below. Have any of you had the time to look into it ?

Regard,
Catalin


> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
> Behalf Of [email protected]
> Sent: Tuesday, June 03, 2014 11:59 AM
> To: [email protected]
> Cc: Sendroiu Adrian-B46904
> Subject: qSymbol when using symbol-file
> 
> Hi,
> 
> In the gdb/gdbserver scenario, gdb is not sending qSymbol packet when
> using "symbol-file", without "file" or "exec-file".
> The steps are:
>   start gdb (with no arguments)
>   (gdb) symbol-file <file>
>   (gdb) target remote <ip>:<port>
>   ->  qSymbol packet is not sent.
> 
> If the "file" command  is used instead of "symbol-file", the qSymbol
> packet is sent to gdbserver.
> 
> The question makes more sense in the following context: Using Eclipse and
> DSF -GDB Hardware Debugging . Here, Eclipse is not using "file", but only
> "symbol-file" ( as explained why here: [1] ).  This  makes qSymbol
> notification not working.
> 
> My questions/comments:
> - In the above scenario, does make sense to enable qSymbol notification
> even when the exec-file is not specified? Here is not required to specify
> the  exec file. Or even in the gdb/gdbserver scenario where the
> application/executable is started by gdbserver on target.
> 
> - For the particular case when some symbol files are added after "target
> remote", gdb is sending qSymbol, even without having the exec file
> specified.  The above proposal would be in sync with this.
> 
> - What would be your other thoughts to fix the qSymbol for the gdb +
> Eclipse with DSF GDB Hardware Debugging scenario ?
> 
> Regards,
> Catalin
> 
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=310304
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.