Frühere Suchanfragen

Keine früheren Suchanfragen

Suchoptionen

Nur verfügbar, wenn angemeldet.
mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Verwaltet von:

Serverstatistik:

1,5 Tsd.
aktive Profile

mastodontech.de: ÜberStatusProfilverzeichnisDatenschutzerklärung

Mastodon: ÜberApp herunterladenTastenkombinationenQuellcode anzeigenv4.4.3

#debugger

0 Beiträge0 Beteiligte0 Beiträge heute
Fortgeführter Thread
*
Aral Balkan

Ah, and also, forgot to mention this change:

Improved:

• Debugging your Kitten app is now easier when you run it using `INSPECT=true kitten …` as the Node runtime is launched using the `--inspect-brk` tag instead of the `--inspect` tag. This means that execution will wait for your debugger (e.g., Chromium’s DevTools at `chrome://inspect`, etc.) to connect before starting the server. This makes it possible to hit breakpoints that might previously have been impossible to reach as they occured before you had a chance to run the debugger.

Full change log:
codeberg.org/kitten/app/src/br

Zusammenfassungskarte des Repositorys kitten/app
Codeberg.orgapp/CHANGELOG.md an mainapp - A web development kit that’s small, purrs, and loves you.
#Kitten#SmallWeb#SmallTech
drmorr

Chapter 7, "Software Breakpoints" of "Building a Debugger" by Sy Brand is done (in Rust)!

github.com/drmorr0/drbug

This chapter was reasonably straightforward. The hardest part was figuring out the right type for my breakpoint sites and convincing the borrow checker it was OK. In the C++ version of this code, Sy just returns a pointer to the breakpoint site and everything is fine.

I tried to do it this way at first but ran into a point in the code where I had to hold an immutable borrow across a mutable borrow. In the C++ code this is fine because they're clearly touching different parts of the code and won't interact, but there's no way to tell the Rust borrow checker that, and there was no way to restructure the code to make it work.

I ended up making the breakpoint sites Clone-able, and then just wrapped the "important"/"shared" bits in Rc<Cell<...>>, which works pretty well aside from a couple dumb mistakes which took me too long to debug.

I also, instead of shelling out to `readelf` in the tests, just used the `elf` crate which already exists for Rust. I expect to rip this out in Chapter 11 when we implement our own ELF support in the debugger, but for now it feels less gross than readelf regex parsing.

Next up, Chapter 8, is Memory and Disassembly! I did a quick sneak peak ahead and discovered that the book relies on an external C++ lib for disassembly; fortunately, the `iced` crate for Rust seems to provide the functionality that we need here:

github.com/icedland/iced

x86 debugger written in Rust. Contribute to drmorr0/drbug development by creating an account on GitHub.
GitHubGitHub - drmorr0/drbug: x86 debugger written in Rustx86 debugger written in Rust. Contribute to drmorr0/drbug development by creating an account on GitHub.
#rust#debugger
*
Piotr Esden-Tempski

The long awaited Black Magic Debug V2.0.0 release is finally here! It is a big update with a lot of improvements and newly supported targets. It pairs very well with bmputil, make sure to give it a try! See release notes for more details. Thanks to everyone who contributed! 🙂 github.com/blackmagic-debug/bl Discuss: github.com/blackmagic-debug/bl #opensource #debugger #electronics #jtag #swd #arm #riscv

*
drmorr

This took surprisingly long given that "all" I was doing was writing some tests, but I'm done with Chapter 6, "Testing Registers with x86 Assembly" of "Building a Debugger" in Rust!

This chapter tests the register-writing code that we wrote in the last chapter, and it also adds an interface to the CLI for reading and writing registers for an attached process.

github.com/drmorr0/drbug

x86 debugger written in Rust. Contribute to drmorr0/drbug development by creating an account on GitHub.
GitHubGitHub - drmorr0/drbug: x86 debugger written in Rustx86 debugger written in Rust. Contribute to drmorr0/drbug development by creating an account on GitHub.
#rust#debugger
Der Teilweise

Is there a kind of how-did-i-end-up-here-debugger?

Example usage:
Website sends signed requests. You want to know how the signature is build.

Set a breakpoint on XMLHttpRequest.send().
Start recording the huge this-depends-on-that-tree.
Perform actions that trigger send.
Select a variable that holds the signature.

The output should be runnable code.
It would set up required state first.
After that (only) the code that had influence on the signature would be printed.

#dev#tool#debugger
drmorr

OK I finished up Chapter 5: Registers from "Building a Debugger". This one was a bit of a doozy.

The book uses number of C++-specific tricks that don't have easy analogues into Rust, so I had to figure out how to convert those in a sensible way. I also forgot (and then was reminded again) about my love/hate relationship with the Rust macro ecosystem.

Also, there are just a LOT OF FREAKING REGISTERS in x86. We'll be implementing support for (checks notes) one hundred and twenty four of them, and that's not all of them.

Anyways I have literally no idea if any of this code works, but that's what chapter 6 is about, supposedly. Sy does include a helpful note at the end of Chapter 5: "The tests will take us down something of a rabbit hole, however, so now would be a great time to take a break." 😂

github.com/drmorr0/drbug

x86 debugger written in Rust. Contribute to drmorr0/drbug development by creating an account on GitHub.
GitHubGitHub - drmorr0/drbug: x86 debugger written in Rustx86 debugger written in Rust. Contribute to drmorr0/drbug development by creating an account on GitHub.
#rustlang#debugger
Antwortete im Thread
Kevin Karhan :verified:

@hisold OFC #Cheats are a way to learn how to "#hack" as in "What if I change the value at this address?"

And I still do recommend anyone interested in #IT and espechally #ITsec to build themselves their own #airgapped #HomeLab to "#FuckAroundAndFindOut!" safely within.

  • Kinda like a "Dojo" (something that costs $$ per hour in terms of a "remote lab" to even be given access in)...

And with #AntiP2W becoming mainstream as well as Players despising #P2W / #PayToWin / #Pay2Win (aka. #P2L / #PayToLoose / #Pay2Loose) as well as literal #gambling on some #Minecraft servers, I don't blame Kids that feel shafted (harder than #Millenials like myself back in the days of #HabboHotel) if they decide to fuck with servers rather than scamming other players…

www.youtube.com- YouTubeAuf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.
*
Piotr Esden-Tempski

Hey everyone! The second Black Magic Debug V2.0.0-rc2 Firmware major stable release candidate is out! We have addressed a bunch of issues in the previous release candidate! Please give this release a try and report any issues you may find! See release notes for details for this release. Thank you everyone who contributed! 🙂 github.com/blackmagic-debug/bl Discuss: github.com/blackmagic-debug/bl #opensource #debugger #electronics #jtag #swd

AngesagtLive-Feeds
Über