Live data from Hacker News

Show HN: Uscope, a new Linux debugger written from scratch

github.com

1–10 of 133 posts

Show HN: Uscope, a new Linux debugger written from scratch

#1
Hi! I've been building a debugger on my nights and weekends because it's fun, and I personally need a better debugger for my work. GDB and LLDB pain me greatly; we can and will do better!

As explained in the README, it's still very early-days and it's not ready for use yet, but check back often because it's improving all the time!

Check out https://calabro.io/uscope for a more detailed explanation.

Thanks for taking a look!

Show HN: Uscope, a new Linux debugger written from scratch
github.com

Re: Show HN: Uscope, a new Linux debugger written from scratch

#2
To clarify “from scratch” as in from basic materials and not “in scratch” as in the MIT graphical programming g system[0]. It appears to be written in Zig[1], which I find interesting for analysis.

0. https://scratch.mit.edu/

1. https://github.com/jcalabro/uscope

Re: Show HN: Uscope, a new Linux debugger written from scratch

#3
post #2

To clarify “from scratch” as in from basic materials and not “in scratch” as in the MIT graphical programming g system[0]. It appears to be written in Zig[1], which I find interesting for analysis. 0. https://scratch.mit.edu/ 1. https://github.com/jcalabro/uscope

lol, I think no one expected a linux debugger to be written in the visual programming language for kids.

Re: Show HN: Uscope, a new Linux debugger written from scratch

#6
It's not clear to me why we'd need a new debugger instead of GDB enhancements. GDB has an extensible, modern C++ codebase with literal decades of hard earned knowledge baked into it.

How are we better off rewriting it, especially if the rewrite isn't memory safe?

Re: Show HN: Uscope, a new Linux debugger written from scratch

#8

It's not clear to me why we'd need a new debugger instead of GDB enhancements. GDB has an extensible, modern C++ codebase with literal decades of hard earned knowledge baked into it. How are we better off rewriting it, especially if the rewrite isn't memory safe?

Consider this part of the post:

>I've been building a debugger on my nights and weeks because it's fun

Post reply on HN