From: Michael Snyder <msnyder@vmware.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "teawater@gmail.com" <teawater@gmail.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [Doc]tracepoint: change *$esp@300 to *(unsigned char *)$esp@300
Date: Tue, 24 Aug 2010 18:07:00 -0000 [thread overview]
Message-ID: <4C740A55.8090804@vmware.com> (raw)
In-Reply-To: <83zkwbnb50.fsf@gnu.org>
Eli Zaretskii wrote:
>> Date: Tue, 24 Aug 2010 10:35:34 -0700
>> From: Michael Snyder <msnyder@vmware.com>
>> CC: Hui Zhu <teawater@gmail.com>,
>> "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>>
>> Eli Zaretskii wrote:
>>>> From: Hui Zhu <teawater@gmail.com>
>>>> Date: Tue, 24 Aug 2010 11:30:03 +0800
>>>> Cc: gdb-patches@sourceware.org
>>>>
>>>> If "unsigned char" is too big, what about *(char *)$esp@300?
>>> "char" is better, but not because of the length.
>>>
>>> However, what I really meant is to ask whether *$esp should indeed
>>> refuse to work, or is that a bug?
>> I imagine it must have worked at one time...
>
> If we-all think now that it's okay for *$esp not to work, then let's
> fix the docs and be done.
I think the reason it doesn't work now is that it's typed as a void pointer.
(gdb) pt $esp
type = void *
Probably it used to be typed as a char * or something.
next prev parent reply other threads:[~2010-08-24 18:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 2:10 Hui Zhu
2010-08-24 3:06 ` Eli Zaretskii
2010-08-24 3:30 ` Hui Zhu
2010-08-24 17:08 ` Eli Zaretskii
2010-08-24 17:35 ` Michael Snyder
2010-08-24 18:00 ` Eli Zaretskii
2010-08-24 18:07 ` Michael Snyder [this message]
2010-08-24 18:37 ` Pedro Alves
2010-08-24 17:33 ` Michael Snyder
2010-08-24 17:58 ` Eli Zaretskii
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=4C740A55.8090804@vmware.com \
--to=msnyder@vmware.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=teawater@gmail.com \
/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