Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: [RFC 06/12] entryval: Display @entry parameters in bt full
Date: Tue, 19 Jul 2011 11:52:00 -0000	[thread overview]
Message-ID: <E1Qj8FY-0007Sq-Hj@fencepost.gnu.org> (raw)
In-Reply-To: <20110719103055.GA21344@host1.jankratochvil.net> (message from	Jan Kratochvil on Tue, 19 Jul 2011 12:30:55 +0200)

> Date: Tue, 19 Jul 2011 12:30:55 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sourceware.org
> 
> GDB internally knows the value of the parameter at the function entry - to be
> able to recover the values.  It has been found out the developers may find it
> useful to be shown the entry values it.  It is an additional feature on top of
> the values recovery.

But then why don't we just show the value at entry in the function
call line?  IOW, show this:

  #8  0x000000000048c50d in execute_command (p=0x22b5720 "maintenance internal-error", from_tty=1) at top.c:438

instead of this:

  #8  0x000000000048c50d in execute_command (p=0x22b573b "", from_tty=1) at top.c:438
	p@entry = 0x22b5720 "maintenance internal-error "

Also show those entry-time values in "info args", as you already
suggested.

This will also fix the annoyance I sometimes bump into, whereby if I
type "bt" some time after stepping into a function, the values of the
parameters are not necessarily those that were actual at the time of
the call (if the function modifies them).

> I think it is separated well enough in the patchset, up to incl. 05/12 it is
> about values recovery, from 06/12 it is about user-accessible entry values.

Sorry, I didn't read the code, only the doco parts and the general
discussion.

Thanks.


  reply	other threads:[~2011-07-19 11:14 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 20:21 Jan Kratochvil
2011-07-18 22:24 ` Daniel Jacobowitz
2011-07-19 10:48   ` Eli Zaretskii
2011-07-19 10:55     ` Jan Kratochvil
2011-07-19 11:52       ` Eli Zaretskii [this message]
2011-07-19 12:17         ` Jakub Jelinek
2011-07-19 16:46           ` Eli Zaretskii
2011-07-19 17:22             ` Jakub Jelinek
2011-08-03 17:27           ` Jan Kratochvil
2011-08-03 17:53             ` Jan Kratochvil
2011-08-03 18:13               ` Jan Kratochvil
2011-08-03 18:36             ` Tom Tromey
2011-08-03 19:43   ` Jan Kratochvil
2011-09-02 17:08   ` [MI RFC] entryval: MI access to entry values [Re: [RFC 06/12] entryval: Display @entry parameters in bt full] Jan Kratochvil
2011-09-13 21:35     ` [MI RFC] entryval: MI access to entry values Jan Kratochvil
2011-09-14  8:50       ` Vladimir Prus
2011-09-14  9:13         ` André Pönitz
2011-09-14  9:20           ` Jan Kratochvil
2011-09-14 10:45             ` André Pönitz
2011-10-03 17:00               ` Tom Tromey
2011-10-03 16:57     ` [MI RFC] entryval: MI access to entry values [Re: [RFC 06/12] entryval: Display @entry parameters in bt full] Tom Tromey
2011-10-03 17:05       ` Vladimir Prus
2011-10-03 17:44         ` Jan Kratochvil
2011-10-03 18:14           ` Joel Brobecker
2011-10-10 16:09           ` André Pönitz
2011-07-19 10:57 ` [RFC 06/12] entryval: Display @entry parameters in bt full Eli Zaretskii
2011-07-19 16:21 ` Tom Tromey

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=E1Qj8FY-0007Sq-Hj@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@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