From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: freindlyuser@hushmail.com, gdb@sourceware.org
Subject: Re: 64bit pointer
Date: Fri, 04 Sep 2009 15:47:00 -0000 [thread overview]
Message-ID: <m31vmmd865.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090903123325.GA24453@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Thu, 3 Sep 2009 14:33:25 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> Yes. Until GDB forbids dereferencing numeric arguments as `int *'
Jan> which IMHO is more confusing than convenient. [Would a patch be
Jan> approved?]
This behavior does seem strange to me.
GDB as a project seems to be somewhat conservative about changing things
like this, though. I don't think I could predict whether anybody would
object, you pretty much have to submit a patch and see who speaks up.
Tom
next prev parent reply other threads:[~2009-09-04 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 12:21 freindlyuser
2009-09-03 12:33 ` Jan Kratochvil
2009-09-04 15:47 ` Tom Tromey [this message]
2009-09-03 13:01 ` Andreas Schwab
2009-09-03 13:27 freindlyuser
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=m31vmmd865.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=freindlyuser@hushmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.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