From: Tom Tromey <tromey@adacore.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tromey@adacore.com>,
Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix DAP stackTrace through frames without debuginfo
Date: Mon, 13 Mar 2023 12:46:39 -0600 [thread overview]
Message-ID: <87bkkwlca8.fsf@tromey.com> (raw)
In-Reply-To: <b912f1e7-4518-1c74-e3ce-622291d046f5@suse.de> (Tom de Vries's message of "Thu, 9 Mar 2023 21:35:15 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> Sorry, yet another error.
I do not understand this one.
Tom> File "/data/vries/gdb/leap-15-4/build/gdb/data-directory/python/gdb/dap/frames.py", line 49, in frame_id
Tom> return _frame_ids[frame]
Tom> KeyError: <gdb.Frame object at 0x7f61b0047bb0>
I don't really know what's going wrong here. I wonder if the new hash
function could be incorrect. Like, if the contents of the frame id
change, causing the hash to change, then this would presumably break the
Python hash table.
Instead of a hash I can change this to use a list I suppose.
Tom
next prev parent reply other threads:[~2023-03-13 18:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 19:48 Tom Tromey
2023-03-06 15:17 ` Tom Tromey
2023-03-09 8:38 ` Tom de Vries
2023-03-09 14:24 ` Tom Tromey
2023-03-09 14:52 ` Tom Tromey
2023-03-09 16:10 ` Tom de Vries
2023-03-09 18:45 ` Tom Tromey
2023-03-09 20:35 ` Tom de Vries
2023-03-13 18:46 ` Tom Tromey [this message]
2023-03-14 13:08 ` Tom Tromey
2023-03-14 13:28 ` Tom de Vries
2023-03-14 14:03 ` 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=87bkkwlca8.fsf@tromey.com \
--to=tromey@adacore.com \
--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).