From: Daniel Jacobowitz <drow@false.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [rfc] expose gdb values to python
Date: Tue, 30 Sep 2008 12:41:00 -0000 [thread overview]
Message-ID: <20080930124105.GA29401@caradoc.them.org> (raw)
In-Reply-To: <1222747562.8567.87.camel@localhost.localdomain>
On Tue, Sep 30, 2008 at 01:06:02AM -0300, Thiago Jung Bauermann wrote:
> I did it this way having in mind the case when a value needs to be
> created at a moment when no file is loaded (and thus an
> architecture/target is not yet determined). This is the same problem
> faced by the expression evaluator, when the user types (say):
>
> (gdb) print 1.2
And I think it should have the same solution. There's a default
architecture for these cases (depending on how GDB was built). If, in
the future, we find another way to handle the print command... then we
can find another way to handle this, too. I suggest that rather than
bending over backwards to avoid the gdbarch.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-09-30 12:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 6:05 Thiago Jung Bauermann
2008-09-20 21:29 ` Tom Tromey
2008-09-21 4:27 ` Daniel Jacobowitz
2008-09-25 4:33 ` Thiago Jung Bauermann
2008-09-25 11:47 ` Daniel Jacobowitz
2008-09-26 2:00 ` Thiago Jung Bauermann
2008-09-26 9:30 ` Eli Zaretskii
2008-09-28 1:19 ` Thiago Jung Bauermann
2008-09-28 18:19 ` Eli Zaretskii
2008-09-29 16:16 ` Thiago Jung Bauermann
2008-09-29 17:00 ` Daniel Jacobowitz
2008-09-30 4:07 ` Thiago Jung Bauermann
2008-09-30 12:41 ` Daniel Jacobowitz [this message]
2008-10-01 3:18 ` Thiago Jung Bauermann
2008-10-01 11:40 ` Daniel Jacobowitz
2008-09-29 18:52 ` Eli Zaretskii
2008-09-26 20:57 ` Daniel Jacobowitz
2008-10-01 5:39 ` Joel Brobecker
2008-10-04 22:14 ` Thiago Jung Bauermann
2008-09-25 4:49 ` Thiago Jung Bauermann
2008-09-26 23:08 ` Tom Tromey
2008-10-01 5:48 ` Joel Brobecker
2008-10-01 15:12 ` Tom Tromey
2008-10-01 16:04 ` Joel Brobecker
2008-10-04 22:21 ` Daniel Jacobowitz
2008-10-05 0:00 ` Tom Tromey
2008-10-06 18:49 ` Joel Brobecker
2008-10-06 21:15 ` Daniel Jacobowitz
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=20080930124105.GA29401@caradoc.them.org \
--to=drow@false.org \
--cc=bauerman@br.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.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