Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: fix debug expression dumping of function call expressions
Date: Fri, 06 Nov 2020 11:38:43 -0700	[thread overview]
Message-ID: <87h7q2ib4c.fsf@tromey.com> (raw)
In-Reply-To: <20201106181859.437662-1-andrew.burgess@embecosm.com> (Andrew Burgess's message of "Fri, 6 Nov 2020 18:18:59 +0000")

Andrew> In this commit I have cleaned up all of the debug-expr.exp files a
Andrew> little, there was a helper function that had clearly been copied into
Andrew> each file, this is now moved into lib/gdb.exp.

Andrew> I've added a gdb.fortran/debug-expr.exp test file, and extended
Andrew> gdb.base/debug-expr.exp to cover the function call case.

This looks good to me.  Thank you for doing this.

Andrew> -  (*pos) += 2;
Andrew>    unsigned nargs = longest_to_int (exp->elts[*pos].longconst);
Andrew> +  (*pos) += 2;

A couple times I have toyed with rewriting struct expression to not be
so incredibly obscure.  However, this is a difficult project :(.  There
are a lot of places to change and I haven't come up with an approach
better than "one enormous patch".

Tom

  reply	other threads:[~2020-11-06 18:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06 18:18 Andrew Burgess
2020-11-06 18:38 ` Tom Tromey [this message]
2020-11-06 20:59   ` Andrew Burgess

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=87h7q2ib4c.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    /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