public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Add label option to proc cu
Date: Thu, 26 Aug 2021 09:38:58 -0400	[thread overview]
Message-ID: <62258296-6132-ff23-cd4c-2f2820249a60@polymtl.ca> (raw)
In-Reply-To: <20210826115605.GA22680@delia>



On 2021-08-26 7:56 a.m., Tom de Vries via Gdb-patches wrote:
> Hi,
> 
> We can use current dwarf assembly infrastructure to declare a label that marks
> the start of the CU header:
> ...
>   declare_labels header_start_cu_a
>   _section ".debug_info"
>   header_start_cu_a : cu {} {
>   }
>   _section ".debug_info"
>   header_start_cu_b : cu {} {
>   }
> ...
> on the condition that we switch to the .debug_info section before, which makes
> this style of use fragile.
> 
> Another way to achieve the same is to use the label as generated by the cu
> proc itself:
> ...
>   variable _cu_label
>   cu {} {
>   }
>   set header_start_cu_a $_cu_label
>   cu {} {
>   }
>   set header_start_cu_b $_cu_label
> ...
> but again that seems fragile given that adding a new CU inbetween will
> silently result in the wrong value for the label.

And this is done by poking in the internals of the framework, not good.

> Add a label option to proc cu such that we can simply do:
> ...
>   declare_labels header_start_cu_a
>   cu { label header_start_cu_a } {
>   }
>   cu { label header_start_cu_b } {
>   }

That looks like the right way to do it.  But can we make it so the
caller doesn't need to use declare_labels?  For example, with rnglists'
-post-header-label switch, it's not needed, so I presume it would be
possible here.

Simon

  reply	other threads:[~2021-08-26 13:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 11:56 Tom de Vries
2021-08-26 13:38 ` Simon Marchi [this message]
2021-08-26 15:16   ` Tom de Vries
2021-08-27 13:24     ` Tom Tromey
2021-08-27 14:13       ` Tom de Vries

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=62258296-6132-ff23-cd4c-2f2820249a60@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).