public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug python/19800] no way to get a frame id from a frame
[not found] <bug-19800-4717@http.sourceware.org/bugzilla/>
@ 2022-06-05 15:26 ` tromey at sourceware dot org
2025-01-11 19:00 ` tromey at sourceware dot org
2025-01-14 23:55 ` tromey at sourceware dot org
2 siblings, 0 replies; 3+ messages in thread
From: tromey at sourceware dot org @ 2022-06-05 15:26 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=19800
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I don't remember the context here any more but I wonder if
it would have been possible to just use the Frame itself,
considering that these are "self inflating frame IDs" anyway.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug python/19800] no way to get a frame id from a frame
[not found] <bug-19800-4717@http.sourceware.org/bugzilla/>
2022-06-05 15:26 ` [Bug python/19800] no way to get a frame id from a frame tromey at sourceware dot org
@ 2025-01-11 19:00 ` tromey at sourceware dot org
2025-01-14 23:55 ` tromey at sourceware dot org
2 siblings, 0 replies; 3+ messages in thread
From: tromey at sourceware dot org @ 2025-01-11 19:00 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=19800
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
The Frame itself can't really be used since it is not hashable.
The DAP code works around this problem... I wonder if it is even
fixable, I vaguely recall convincing myself that a Frame can't
really be made hashable.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug python/19800] no way to get a frame id from a frame
[not found] <bug-19800-4717@http.sourceware.org/bugzilla/>
2022-06-05 15:26 ` [Bug python/19800] no way to get a frame id from a frame tromey at sourceware dot org
2025-01-11 19:00 ` tromey at sourceware dot org
@ 2025-01-14 23:55 ` tromey at sourceware dot org
2 siblings, 0 replies; 3+ messages in thread
From: tromey at sourceware dot org @ 2025-01-14 23:55 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=19800
--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
I pushed a couple minor updates to my branch btw.
Probably some of the ForEachMacros could be removed now,
I didn't dig.
I wonder if some of the bin-packing problems could be
solved by changing penalties.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-01-14 23:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-19800-4717@http.sourceware.org/bugzilla/>
2022-06-05 15:26 ` [Bug python/19800] no way to get a frame id from a frame tromey at sourceware dot org
2025-01-11 19:00 ` tromey at sourceware dot org
2025-01-14 23:55 ` tromey at sourceware dot org
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).