Qt, Linux and everything: Debugging Qt WebAssembly
http://qtandeverything.blogspot.com/2025/12/debugging-qt-webassembly-dwarf.html
Durin is a library for reading and writing the Dwarf debugging format
https://github.com/tmcgilchrist/durin
#HackerNews #Durin #Dwarf #Debugging #Library #Programming #OpenSource #GitHub
When Your Hash Becomes a String: Hunting Ruby's Million-to-One Memory Bug
https://mensfeld.pl/2025/11/ruby-ffi-gc-bug-hash-becomes-string/
#HackerNews #Ruby #Memory #Bug #Hashing #FFI #Programming #Debugging
Debugging BeagleBoard USB boot with a sniffer: fixing omap_loader on modern PCs
#HackerNews #Debugging #BeagleBoard #USB #omap_loader #sniffer #modernPCs
From 400 Mbps to 1.7 Gbps: A WiFi 7 Debugging Journey
https://blog.tymscar.com/posts/wifi7speedhunt/
#HackerNews #WiFi7 #Debugging #Journey #SpeedTest #Technology #Networking
Claude Code Can Debug Low-Level Cryptography
https://words.filippo.io/claude-debugging/
#HackerNews #ClaudeCode #Debugging #Cryptography #LowLevel #TechNews
wannabe eldritch entity :v_bi:
boosted
Pre-LLM assisted debugging tools.
Your weary 'net denizen
boosted
A crippling and subtle timing bug in the onboard software of the Jupiter bound JUICE spacecraft. It takes the right stuff to troubleshoot such an issue with the running system 200 million km away.
https://www.esa.int/Enabling_Support/Operations/Juice_team_resolves_anomaly_on_approach_to_Venus
A crippling and subtle timing bug in the onboard software of the Jupiter bound JUICE spacecraft. It takes the right stuff to troubleshoot such an issue with the running system 200 million km away.
https://www.esa.int/Enabling_Support/Operations/Juice_team_resolves_anomaly_on_approach_to_Venus
🥳 New Kitten Release
Housekeeping:
• Updated runtime version to Node version 22.18.0 (latest LTS).
• Removed --experimental-global-customevent in node launch command (as CustomEvent is no longer behing the CLI flag since Node v19.0.0)
• Renamed --experimental-loader flag to --loader as the experimental prefix is no longer required.
Enjoy!
💕
#Kitten#KittenRelease #SmallWeb#SmallTech #web #dev#HTML#JavaScript#CSS#NodeJS
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:
https://codeberg.org/kitten/app/src/branch/main/CHANGELOG.md#2025-08-12
#Kitten #SmallWeb #SmallTech #NodeJS #debugger #debugging #web #dev #JavaScript
🐍 Decode Any Python Code With This 5-Step Method
｢ It’s rare to write all the original code in an application yourself, and even rarer for an application to be completely rewritten from scratch. More likely, your workflow will involve working with code that was written by someone else (who may no longer be available to explain it) and iterated on by others (who also might be out of reach) long before it ever appears on your screen ｣
https://thenewstack.io/decode-any-python-code-with-this-5-step-method/
@jbz I could understand the code by just reading it from top to bottom. In reality that would not work because i stop reading at the line "import pandas as pd"
🐍 Decode Any Python Code With This 5-Step Method
｢ It’s rare to write all the original code in an application yourself, and even rarer for an application to be completely rewritten from scratch. More likely, your workflow will involve working with code that was written by someone else (who may no longer be available to explain it) and iterated on by others (who also might be out of reach) long before it ever appears on your screen ｣
https://thenewstack.io/decode-any-python-code-with-this-5-step-method/
🥳 Xdebug 3.4.5 Released!
🐛 This is a bug fix release.
🧬 One fix addresses crashes when using Xdebug's debugger with (nested) Fibers.
↪️ A second bug addresses an issue where, while debugging, Xdebug sometimes calls get property hooks which can then update and change the object's state.
📄 The full list of changes can be found on the updates page: https://xdebug.org/announcements/2025-07-14
I need help. First the question: On #FreeBSD, with all ports built with #LibreSSL, can I somehow use the #clang #thread #sanitizer on a binary actually using LibreSSL and get sane output?
What I now observe debugging #swad:
- A version built with #OpenSSL (from base) doesn't crash. At least I tried very hard, really stressing it with #jmeter, to no avail. Built with LibreSSL, it does crash.
- Less relevant: the OpenSSL version also performs slightly better, but needs almost twice the RAM
- The thread sanitizer finds nothing to complain when built with OpenSSL
- It complains a lot with LibreSSL, but the reports look "fishy", e.g. it seems to intercept some OpenSSL API functions (like SHA384_Final)
- It even complains when running with a single-thread event loop.
- I use a single SSL_CTX per listening socket, creating SSL objects from it per connection ... also with multithreading; according to a few sources, this should be supported and safe.
- I can't imagine doing that on a *single* thread could break with LibreSSL, I mean, this would make SSL_CTX pretty much pointless
- I *could* imagine sharing the SSL_CTX with multiple threads to create their SSL objects from *might* not be safe with LibreSSL, but no idea how to verify as long as the thread sanitizer gives me "delusional" output 😳
For two days straight, I just can't reproduce #swad #crashing with *anything* in place (#clang #sanitizer instrumentation, attached #debugger like #lldb) that could give me the slightest hint what's going wrong. 😡
But it *does* crash when "unobserved". And it looks like this is happening a lot sooner (or, more often?) when using #LibreSSL ... but I also suspect this could be a red herring in the end.
Situation reminds me of my physics teacher back at school, who used to say something in german I just can't ever forget:
"Wer misst, misst Mist."
Feeble attempt in english would be "the one who measures measures crap", it was his humorous way to bring one consequence of #Heisenberg's indeterminacy principle to the point. And indeed, #debugging computer programs always suffers from similar problems...
Visualize and debug Rust programs with a new lens