* GSoC 2026: Improving Rust debugging support in GDB
@ 2026-03-10 2:46 Horne, Preston M
2026-03-12 17:23 ` Tom Tromey
0 siblings, 1 reply; 2+ messages in thread
From: Horne, Preston M @ 2026-03-10 2:46 UTC (permalink / raw)
To: gdb
[-- Attachment #1: Type: text/plain, Size: 724 bytes --]
Hi all,
My name is Preston and I'm a comp sci master's student at Vanderbilt University. I'm interested in contributing to GDB through Google Summer of Code 2026 and would appreciate some advice/mentorship on a project proposal.
The area I'm drawn to initially is improving the experience of debugging Rust programs. I noticed that the GDB docs Rust section (https://sourceware.org/gdb/current/onlinedocs/gdb.html/Rust.html) lists several limitations, and I'd like to understand whether working on that kind of thing, or other Rust improvements, would be a realistic and useful GSoC project? I'm very comfortable with C++ as that is what I spent the majority of my undergraduate courses studying.
Thanks,
Preston
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: GSoC 2026: Improving Rust debugging support in GDB
2026-03-10 2:46 GSoC 2026: Improving Rust debugging support in GDB Horne, Preston M
@ 2026-03-12 17:23 ` Tom Tromey
0 siblings, 0 replies; 2+ messages in thread
From: Tom Tromey @ 2026-03-12 17:23 UTC (permalink / raw)
To: Horne, Preston M via Gdb; +Cc: Horne, Preston M
>>>>> Horne, Preston M via Gdb <gdb@sourceware.org> writes:
> The area I'm drawn to initially is improving the experience of
> debugging Rust programs. I noticed that the GDB docs Rust section
> (https://sourceware.org/gdb/current/onlinedocs/gdb.html/Rust.html)
> lists several limitations, and I'd like to understand whether working
> on that kind of thing, or other Rust improvements, would be a
> realistic and useful GSoC project? I'm very comfortable with C++ as
> that is what I spent the majority of my undergraduate courses
> studying.
I think the main difficulty is that the major issues with Rust debugging
are all basically due to compiler holes -- the compiler not emitting
DWARF for various constructs. This is why calls via traits don't always
work, why operator overloading doesn't work in gdb (really the same as
the trait issue), why some "local" name lookups fail, etc.
For bugs like that, you would have to fix the compiler first. However
that's also non-trivial; for instance the trait issue means first
patching LLVM.
Also some of the problems mentioned in that node aren't really worth
fixing IMO.
So I guess it depends on what exactly you would envision doing. And
maybe that's between you & your mentor (I have no idea how that works).
There's also the open Rust bugs:
https://sourceware.org/bugzilla/buglist.cgi?component=rust&list_id=102021&product=gdb&resolution=---
Some of these are probably reasonable to solve. Like the "varobj" bug
(if it exists) would be useful for IDEs. But it's kind of ugly
programming; varobj is arguably the currently worst code in gdb.
HTH,
Tom
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-03-12 17:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-03-10 2:46 GSoC 2026: Improving Rust debugging support in GDB Horne, Preston M
2026-03-12 17:23 ` Tom Tromey
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).