The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,860 other subscribers

Archive for the ‘Debugging’ Category

b0rk (Julia Evans) on Twitter: “integer overflow”

Posted by jpluimers on 2025/10/16

Even seemingly simple data structures are worth explaining, especially when debugging. So I was glad with the explanation of [Wayback/Archive] Julia Evans on Twitter: “integer overflow”:

Read the rest of this entry »

Posted in Conference Topics, Conferences, Debugging, Development, Event, Software Development | Leave a Comment »

“The Pocket Guide to Debugging” zine and Debugging Puzzels by b0rk (Julia Evans)

Posted by jpluimers on 2025/09/10

I forgot scheduling this post, but it is still very relevant: about the debugging related materials by b0rk (Julia Evans) as they are not limited to just “The Pocket Guide to Debugging”.

It is excellent material to learn at home, work or be used during education.

Before the Elmo* takeover, she mainly used Twitter to post beta material and later the final versions. Easiest queries to find back the Tweets are:

Here are some of links found via the above lists of tweets:

Read the rest of this entry »

Posted in Debugging, Development, Software Development | Leave a Comment »

Important debugging strategy from b0rk: “after the bug is fixed: write a postmortem”

Posted by jpluimers on 2025/07/24

[Wayback/Archive] Julia Evans on Twitter: “after the bug is fixed: write a postmortem”

title: write a postmortem For very tricky bugs, writing up an explanation of what went wrong and how it was fixed is an amazing way to share knowledge and make sure I really understand it. Ways I've done this in the past: * complain about it in the internal chat! (so people can search for it!) * write a quick explanation in the pull request description * write a fun blog post telling my tale of woe! * for really important work bugs, write a 5-page document with graphs explaining all the weird stuff I learned along the way

–jeroen

Posted in Conference Topics, Conferences, Debugging, Development, Event, Software Development | Leave a Comment »

🔎Julia Evans🔍 on Twitter: “debugging strategy: use sounds or pictures I’m still not satisfied with the examples in this one, I’d love to hear examples of how you use visualizations or sounds to debug https://t.co/5DOxshi8QN” / Twitter

Posted by jpluimers on 2025/06/17

[Wayback/Archive] Julia Evans on Twitter: “debugging strategy: use sounds or pictures I’m still not satisfied with the examples in this one, I’d love to hear examples of how you use visualizations or sounds to debug”

title: use sounds or pictures When you're dealing with a lot of data (like in a game for example), sometimes text isn't the best way for your brain to process it! computer: "<thousands of lines of log messages>" person: "ugh I can't read all this!" computer: boop boop beep beep boop person: "wait, that pattern is super irregular..." Some things you could try: * play a sound every time an event happens! * add red outlines around every HTML element! * display an image representing some data!

Posted in Debugging, Development, Software Development | Leave a Comment »

b0rk on Twitter about getting unstuck: “debugging strategy: do the annoying thing”

Posted by jpluimers on 2025/06/04

Not just about getting unstuck during debugging: making progress is often about doing “the annoying thing”.

[Wayback/Archive] Julia Evans on Twitter: “debugging strategy: do the annoying thing”:

Read the rest of this entry »

Posted in Debugging, Development, Software Development | Leave a Comment »

b0rk: “debugging strategy: jump into a REPL” / Twitter

Posted by jpluimers on 2025/05/28

[Wayback/Archive] 🔎Julia Evans🔍 on Twitter: “debugging strategy: jump into a REPL” (more platforms in the replies to the Tweet)

title: jump into a REPL In dynamic languages (like Python / Ruby / JS), you can jump into an interactive console at any point in your code. Here's how to do it in a frontend Javascript program: 1. edit your code code: ``` my_var = call_some_function() debugger; ``` 2. refresh the page 3. play around in the developer tools console! you can call any function you want / try out fixes! How to do it in other languages: Ruby: `binding.pry` Python: `import pdb; pdb.set_trace()`

Read the rest of this entry »

Posted in Debugging, Development, Software Development | Leave a Comment »

Debugging Win32 binaries in Ghidra via Wine

Posted by jpluimers on 2025/05/20

For my link archive: [Wayback/Archive] Debugging Win32 binaries in Ghidra via Wine

[Wayback/Archive] Ghidra is a cross-platform reverse-engineering and binary analysis tool, with recent versions including support for dynamic analysis. I want to try using it as a replacement for IDA Pro in reverse-engineering of Win32 binaries, but hit bugs related to address space detection when running gdbserver with Wine ([Wayback/Archive] ghidra#4534).

This post contains custom GDB commands that allow Ghidra to query the Linux process ID and memory maps of a Win32 target process running in 32-bit Wine on a 64-bit Linux host.

Via [Wayback/Archive] Ptrace Security GmbH on Twitter: “Debugging Win32 binaries in Ghidra via Wine #Pentesting #Debugging #CyberSecurity #Infosec”.

--jeroen

Posted in Debugging, Development, Software Development, Windows Development | Tagged: , , , | Leave a Comment »

One of the marvels from b0rk on Twitter is some 40 pages of debugging strategies: by now it should be a fully fledged zine

Posted by jpluimers on 2025/03/11

[Wayback/Archive] 🔎Julia Evans🔍 on Twitter: “so far we have about 40 pages of debugging strategies and trying to organize them is a struggle :) here’s a draft of the table of contents (though it’s SO FAR from being done, note the “unsorted pages” section haha)”:

Image

Table of contents text (via Google Lens):

Read the rest of this entry »

Posted in Agile, Debugging, Development, Software Development, Unit Testing | Leave a Comment »

Skip line while debugging in Chrome developer tools – Stack Overflow

Posted by jpluimers on 2024/03/27

[Wayback/Archive] Skip line while debugging in Chrome developer tools – Stack Overflow (thanks [Wayback/Archive] Matas Vaitkevicius for both asking and answering):

Last comment from dev says:
We’re going to hold off on this feature for now. It’s complexity is high and it’s not common enough a workflow. One could also just comment out the lines and hit ctrl-s to get the same effect, pretty much. Status: WontFix –
The workaround is to comment out the line you want to skip and press Ctrl+S.

The problem is that the workaround fails when you have used the Chrome Dev Tools to format the source code: then you cannot edit the formatted code.

The workaround for that is cumbersome, but doable as in this bug report:

Read the rest of this entry »

Posted in Chrome, Debugging, Development, Google, JavaScript/ECMAScript, Power User, Scripting, Software Development, Web Development | Leave a Comment »

BitSavers added some more Borland documentation in 2022 (most relevant for me: Assembler, Debugger, Profiler)

Posted by jpluimers on 2024/02/28

Below is a list of the Borland documentation that BitSavers added in 2022, ordered by relevance to me (and how I finally asked Peter Sawatzki if he still had the monochrome TDVIDEO.DLL he wrote for Turbo Debugger 3.0 for Windows):

Read the rest of this entry »

Posted in 8087, Algorithms, Assembly Language, Borland C++, C, C++, Debugging, Development, Floating point handling, Profiling, Software Development, Turbo Assembler, Turbo C, Turbo Debugger, Turbo Profiler, x86 | Leave a Comment »