Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 5/7] [gdb] Use block::super_blocks
Date: Fri, 24 Apr 2026 23:24:45 +0200	[thread overview]
Message-ID: <decad61b-175d-416a-acea-052a89397389@suse.de> (raw)
In-Reply-To: <87y0icnx1b.fsf@tromey.com>

On 4/24/26 6:27 PM, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
> 
> Tom> Use block::super_blocks in a few locations to simplify code.
> 
> Tom> -    for (const block *b = get_selected_block (0);
> Tom> -	 b != nullptr;
> Tom> -	 b = b->superblock ())
> Tom> +    for (auto b : block::super_blocks (get_selected_block (0)))
> 
> Why not "get_selected_block(0)->super_blocks ()" here?

Because get_selected_block (0) might be nullptr.

I actually checked with an assert:
...
diff --git a/gdb/ada-lang.c b/gdb/ada-lang.c
index 71a338ce17e..76639685977 100644
--- a/gdb/ada-lang.c
+++ b/gdb/ada-lang.c
@@ -13825,6 +13825,7 @@ class ada_language : public language_defn
      /* Search upwards from currently selected frame (so that we can
         complete on local vars.  */

+    gdb_assert (get_selected_block (0) != nullptr);
      for (const block *b = get_selected_block (0);
  	 b != nullptr;
  	 b = b->superblock ())
...
and it triggers in gdb.dwarf2/ada-cold-name.exp.

Thanks,
- Tom

  reply	other threads:[~2026-04-24 21:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23  6:35 [PATCH 0/7] [gdb] Add superblocks range loops Tom de Vries
2026-04-23  6:35 ` [PATCH 1/7] [gdb] Use block::function_block Tom de Vries
2026-04-23 14:33   ` Tom Tromey
2026-04-24 12:19     ` Tom de Vries
2026-04-23  6:35 ` [PATCH 2/7] [gdbsupport] Add parameterless iterator_range constructor Tom de Vries
2026-04-23 14:34   ` Tom Tromey
2026-04-24 12:20     ` Tom de Vries
2026-04-23  6:35 ` [PATCH 3/7] [gdbsupport] Factor out base_next_iterator Tom de Vries
2026-04-30 16:24   ` Simon Marchi
2026-04-30 19:09     ` Simon Marchi
2026-05-01 12:57       ` Tom Tromey
2026-05-01 13:20       ` Tom de Vries
2026-05-01 13:15     ` Tom de Vries
     [not found]   ` <87340kpbwx.fsf@tromey.com>
2026-04-30  4:49     ` Tom de Vries
2026-05-01 12:54       ` Tom de Vries
2026-05-01 13:00     ` Tom de Vries
2026-04-23  6:35 ` [PATCH 4/7] [gdb] Add block::superblocks Tom de Vries
2026-04-27 11:11   ` Jan Vrany
2026-05-01 13:06     ` Tom de Vries
2026-04-30 16:24   ` Simon Marchi
2026-05-01 13:19     ` Tom de Vries
2026-04-23  6:35 ` [PATCH 5/7] [gdb] Use block::super_blocks Tom de Vries
2026-04-24 16:27   ` Tom Tromey
2026-04-24 21:24     ` Tom de Vries [this message]
2026-04-23  6:35 ` [PATCH 6/7] [gdb] Add block::function_blocks Tom de Vries
2026-04-23  6:35 ` [PATCH 7/7] [gdb] Use block::function_blocks 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=decad61b-175d-416a-acea-052a89397389@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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