From: Mukesh Rathor <todfod@hotmail.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: offset of a struct field (qSymbol)
Date: Thu, 02 Oct 2008 00:24:00 -0000 [thread overview]
Message-ID: <BAY144-W134C6222C0B2FDCFC195A3DD3D0@phx.gbl> (raw)
In-Reply-To: <20081001222510.GA13722@caradoc.them.org>
----------------------------------------
> Date: Wed, 1 Oct 2008 18:25:10 -0400
> From: drow@false.org
> To: msnyder@vmware.com
> CC: todfod@hotmail.com; gdb@sourceware.org
> Subject: Re: offset of a struct field (qSymbol)
>
> On Wed, Oct 01, 2008 at 03:19:04PM -0700, Michael Snyder wrote:
>> There is a syntax for gdb to send an expression to the
>> server, and have the server evaluate it. Perhaps we could
>> simply reverse that syntax, so that the server could send
>> an expression to gdb, and have gdb evaluate it and send
>> back the answer?
>
> IMO this is a bad idea. It's too ambiguous, and it will breed remote
> servers that rely on quirks in a particular version of the GDB
> expression parser.
>
> I've worked with some other debug tools that worked this way and it
> was a terrible headache.
I managed to get by. Basically, I ask the user to lookup the value manually, and then use monitor to send the info to gdbserver. The monitor cmd really helped simplify things.
>
> --
> Daniel Jacobowitz
> CodeSourcery
_________________________________________________________________
See how Windows Mobile brings your life together—at home, work, or on the go.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/
prev parent reply other threads:[~2008-10-02 0:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 1:51 Mukesh Rathor
2008-10-01 11:55 ` Daniel Jacobowitz
2008-10-01 22:20 ` Michael Snyder
2008-10-01 22:25 ` Daniel Jacobowitz
2008-10-02 0:24 ` Mukesh Rathor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BAY144-W134C6222C0B2FDCFC195A3DD3D0@phx.gbl \
--to=todfod@hotmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox