From: Michel METZGER <michel.metzger@st.com>
To: tromey@redhat.com
Cc: gdb@sourceware.org
Subject: Re: Side effect of set print address on python API
Date: Fri, 09 Apr 2010 17:31:00 -0000 [thread overview]
Message-ID: <4BBF6435.2090601@st.com> (raw)
In-Reply-To: <m36340oa1d.fsf@fleche.redhat.com>
Tom Tromey wrote:
>>>>>> "Michel" == Michel METZGER <michel.metzger@st.com> writes:
>
> Michel> (gdb) set print address off
> Michel> (gdb) python print len(str(gdb.selected_frame().read_var("argv")))
> Michel> 0
>
> Michel> It's not a blocking issue for me but I guess this is not the expected
> Michel> behavior ;)
>
> It does seem odd. Could you file a bug report for this?
>
> Tom
>
Here it is:
http://sourceware.org/bugzilla/show_bug.cgi?id=11482
Michel.
prev parent reply other threads:[~2010-04-09 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 21:16 Michel METZGER
2010-04-09 17:03 ` Tom Tromey
2010-04-09 17:31 ` Michel METZGER [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=4BBF6435.2090601@st.com \
--to=michel.metzger@st.com \
--cc=gdb@sourceware.org \
--cc=tromey@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