Lingolol

0 posts0 participants0 posts today

OlimexWCH 32-bit microcontrollers and tools are available now at <a href="http://olimex.com" rel="nofollow noopener noreferrer" translate="no" target="_blank">http://olimex.com</a> <a href="https://olimex.wordpress.com/2025/03/24/wch-32-bit-risc-v-microcontrollers-and-tools-in-stock/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://olimex.wordpress.com/2025/03/24/wch-32-bit-risc-v-microcontrollers-and-tools-in-stock/</a> <a href="https://mastodon.social/tags/riscv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#riscv</a> <a href="https://mastodon.social/tags/wch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wch</a> <a href="https://mastodon.social/tags/ch32v003" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ch32v003</a> <a href="https://mastodon.social/tags/programmer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programmer</a> <a href="https://mastodon.social/tags/debugger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debugger</a>

Piotr Esden-TempskiHey everyone! The first Black Magic Debug V2.0.0-rc1 Firmware major stable release candidate is out! This release is quite a massive step forward with a lot of new functionality! Please give this release candidate a try and report any issues you may find! See release notes for details for this release candidate. Thank you everyone who contributed! 🙂 <a href="https://github.com/blackmagic-debug/blackmagic/releases/tag/v2.0.0-rc1" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/blackmagic-debug/blackmagic/releases/tag/v2.0.0-rc1</a> Discuss: <a href="https://github.com/blackmagic-debug/blackmagic/discussions/2045" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/blackmagic-debug/blackmagic/discussions/2045</a> <a href="https://chaos.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://chaos.social/tags/debugger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debugger</a> <a href="https://chaos.social/tags/electronics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#electronics</a> <a href="https://chaos.social/tags/jtag" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#jtag</a> <a href="https://chaos.social/tags/swd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swd</a>

chnThe <a href="https://mastodon.art/tags/github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#github</a> repository of my <a href="https://mastodon.art/tags/sega" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sega</a> <a href="https://mastodon.art/tags/mastersystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mastersystem</a> and <a href="https://mastodon.art/tags/gamegear" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gamegear</a> <a href="https://mastodon.art/tags/emulator" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#emulator</a> called "Masterlator" is now public 🙂 I've rewritten the code in proper C++, use <a href="https://mastodon.art/tags/cmake" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cmake</a> as the build system, utilize <a href="https://mastodon.art/tags/sdl2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sdl2</a> and added a new <a href="https://mastodon.art/tags/debugger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debugger</a> with <a href="https://mastodon.art/tags/wladx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wladx</a> compatible *.sym file support, memory viewer and tile/sprite viewer. It's rather basic now but will hopefully be a good tool for <a href="https://mastodon.art/tags/homebrew" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homebrew</a> game <a href="https://mastodon.art/tags/development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#development</a> in the future.<a href="https://github.com/chn-dev/MasterlatorSDL/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/chn-dev/MasterlatorSDL/</a><a href="https://www.chn-dev.net/Projects/Masterlator/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.chn-dev.net/Projects/Masterlator/</a>

blake shaw 🇵🇸Cue quarterly <a href="https://functional.cafe/tags/Haskell" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Haskell</a> community meltdown To be fair, I think Haskell will continue to fill the niche it filled ~10 years ago, around the time it started to get mainstream hype. Small teams of skilled devs delivering robust products that would normally require much larger teams to maintain will continue to prevail. Purely functional lazy programming was never bound for world domination in an economy which is antagnostic to curiosity, creativity and truths.On the other hand, I have the feeling that we're going to see more and more Haskellers-turned-Rustaceans come to realize that <a href="https://functional.cafe/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> does little to alleviate the primary barrier to Haskell's wider success -- fast and predictable turnaround time for projects developing cutting-edge technologies -- and will wind up going the same route as some major Haskell projects such as <a href="https://functional.cafe/tags/Unison" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Unison</a> and <a href="https://functional.cafe/tags/Idris" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Idris</a> have in recent years, which is to try <a href="https://functional.cafe/tags/Chez" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Chez</a> Scheme, only to discover that it allows them to release blazing fast functional programs on a generic foundation where major breaking changes are practically non-existent, providing incredible flexibility while significantly reducing dependencies by dint of the ad-hoc tooling that falls out of the bottom of <a href="https://functional.cafe/tags/scheme" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scheme</a>. Not to mention the joys that come from near-instant startup times, some of the fastest compile time you've ever encountered, fully-customizable interactive development and a surgical <a href="https://functional.cafe/tags/debugger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debugger</a> that rivals Haskell in scheer fun. Yesterdays naysayers will become tomorrow's enthusiastic bootstrappers. Or a at least a boy can dream.That said, in all seriousness I don't think Scheme will ever reach the heights of Haskell's moderate commercial success. But I do think that projects built on Scheme, like Unison, will get a leg up and eventually surpass it, and interest in <a href="https://functional.cafe/tags/lisp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lisp</a> will only grow.<a href="https://nitter.net/graninas/status/1656519682822746113?cursor=NwAAAPAoHBlWgoCxgZ7Grf0tgsCz2c64l_0tjIC2pczQo_0thIC9xfeLvv0tgoCx4eq3tv0tJQISFQQAAA#r" rel="nofollow noopener noreferrer" target="_blank">https://nitter.net/graninas/status/1656519682822746113?cursor=NwAAAPAoHBlWgoCxgZ7Grf0tgsCz2c64l_0tjIC2pczQo_0thIC9xfeLvv0tgoCx4eq3tv0tJQISFQQAAA#r</a>

eg0n ✅You send a string of 9000 A's and see the telltale 1010 pattern in the memory dump after the program crashes. You frantically check the <a href="https://defcon.social/tags/debugger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debugger</a>, but the memory address for the <a href="https://defcon.social/tags/overflow" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#overflow</a> seems random everytime. But wait, if you add 1C to EAX, you get the start of where memory was overwritten everytime. Just to be safe you put in a couple 0x90s to get a nice <a href="https://defcon.social/tags/nop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nop</a> sled into your <a href="https://defcon.social/tags/shellcode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#shellcode</a>. You lower your hoodie and run your hand through your hair. Damn you're good.<a href="https://defcon.social/tags/hacker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hacker</a> <a href="https://defcon.social/tags/synthesizer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#synthesizer</a> <a href="https://defcon.social/tags/music" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#music</a>

Marcus Botacin[Paper of the day][#8] Debugger-oriented <a href="https://infosec.exchange/tags/decompilation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#decompilation</a>. Decompilation is hard, but we can make it practical by skipping the hard constructions. In this paper, we show how we can construct a <a href="https://infosec.exchange/tags/decompiler" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#decompiler</a> extension on top of the <a href="https://infosec.exchange/tags/GDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GDB</a> <a href="https://infosec.exchange/tags/debugger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debugger</a> and how to use it to skip <a href="https://infosec.exchange/tags/malware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#malware</a> <a href="https://infosec.exchange/tags/unpacking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unpacking</a> and decompiling the extracted <a href="https://infosec.exchange/tags/payload" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#payload</a>.Academic paper: <a href="https://dl.acm.org/doi/10.1145/3375894.3375895" rel="nofollow noopener noreferrer" target="_blank">https://dl.acm.org/doi/10.1145/3375894.3375895</a> Archived version: <a href="https://secret.inf.ufpr.br/papers/roots_revenge.pdf" rel="nofollow noopener noreferrer" target="_blank">https://secret.inf.ufpr.br/papers/roots_revenge.pdf</a> Code: <a href="https://github.com/marcusbotacin/Reverse.Engineering.Engine" rel="nofollow noopener noreferrer" target="_blank">https://github.com/marcusbotacin/Reverse.Engineering.Engine</a>

Recent searches

Search options

Administered by:

Server stats:

#debugger