The Wiert Corner – irregular stream of stuff

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

  • My badges

  • Twitter Updates

    • RT @jamescrabtree: Unexpectedly good gag at the top of this good as expected Krastev @ftopinion piece today. "Central European populists… 14 minutes ago
    • RT @nuget: 📢 For .NET Docker users, we have published new images that mitigate these issues by using a pre-release version of the Debian ca… 16 minutes ago
    • RT @KevlinHenney: Something that's often puzzled me in some Twitter bios is the claim that RTs from that account are not endorsements 🤔 So… 17 minutes ago
    • RT @JohnHuizinga3: Wij woonden hier met een goede buur die 2500m startbaan mocht gebruiken. MAA gebruikt 250m asfalt als extra start/landin… 20 minutes ago
    • RT @mzelst: Onderstaande tweet klopt dus niet. En over een uur (10:00) komt prof. Snijder uitleggen waar volgens hem de onduidelijkheid zit… 23 minutes ago
  • My Flickr Stream

  • Pages

  • All categories

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

    Join 2,230 other followers

Archive for January 15th, 2020

ρσℓα¢ķ͌͌͌͌͌͌͌͌͌͌͌͌͌͌ on Twitter : “The PowerShell console history file isn’t just useful for DFIR peeps, red team-ers should check it too! 4096 entries by default, here’s the path…”

Posted by jpluimers on 2020/01/15

Not sure why, but I checked a few of my systems and no  file at %userprofile%\AppData\Roaming\Microsoft\Windows\PowerShell\PSReadline\ConsoleHost_history.txt

Heck: no ConsoleHost_history.txt files on those systems anywhere.

[WayBack] ρσℓα¢ķ͌͌͌͌͌͌͌͌͌͌͌͌͌͌ on Twitter : “The PowerShell console history file isn’t just useful for DFIR peeps, red team-ers should check it too! 4096 entries by default, here’s the path: %userprofile%\AppData\Roaming\Microsoft\Windows\PowerShell\PSReadline\ConsoleHost_history.txt”


Read the rest of this entry »

Posted in CommandLine, Power User, PowerShell, PowerShell | Leave a Comment »

Drawbacks for separating TDS/TD32 symbol information in separate file for your Delphi applications? What about Visual Studio?

Posted by jpluimers on 2020/01/15

A while ago this interesting question came by: [WayBack] Delphi XE2 has got the Linking option “Place debug information in separate TDS file” … Does this have any adverse effects for Win32 Delphi executables? – Thomas Mueller (dummzeuch) – Google+

The answer is “no”.

By about mid 2018, the same holds for Visual Studio and PDB symbol information.


Since long ago (I think about Delphi 2), the Delphi debugger understands TDS (historically also known as TD32) Turbo Debugger Symbol Information which can be either in the .EXE or in a separate .TDS file with the same name and directory as the .EXE.

Many other tools also know how to get the symbols from either place, see for instance TD32-TDS-SYMBOL-INFORMATION.

The advantage of keeping it in the EXE is that it is easier to ship to clients. Unless you do not want the clients to have it. Then it is easier to separate it in a file.

David Heffernan raises an important point though, as many people confuse these two topics:

  • the presence of Debug Symbols
  • the code generation of extra run-time checks and debug-assistance (like stack frames)

This is caused by both of the above usually being enabled in DEBUG mode and disabled in RELEASE mode.

However, nothing prevents you from generating the Debug Symbols in RELEASE mode, and they can highly help track down customer problems.

This is David’s comment:

There’s a common myth that “debug builds” perform worse than “release builds”.

Whether or not debug information is generated is completely independent from the performance of the code.

Visual Studio

For a long time, EXE files generated by Microsoft Tools could only include .DBG symbol information, but no .PDB symbol information.

[WayBack] executable – Embed .pdb debug symbol information into an .exe file in Visual Studio – Stack Overflow. Especially read the comments about:


Posted in Debugging, Delphi, Development, MAP Symbol Information, Software Development, TD32/TDS Symbol information | Leave a Comment »

How Douglas Engelbart Invented the Future | Innovation | Smithsonian

Posted by jpluimers on 2020/01/15

Two decades before the personal computer, a shy engineer unveiled the tools that would drive the tech revolution

Don’t read this as a historic piece, but as the potential we are still going to experience what was not just sketched by a true visionary in 1968, but also demonstrated back then: [Archive.isHow Douglas Engelbart Invented the Future | Innovation | Smithsonian.

I am including one of the pictures below by Christie Hemm Klok that shows how far Engelbart was ahead of his time: not his initial invention of an input device (the mouse) “chord” kind.

After that, read about his 1968 presentation: The Mother of All Demos – Wikipedia

Finally, watch the video below, well worth watching the more than one and a half hours.



Read the rest of this entry »

Posted in Development, Future, Hardware, History, Network-and-equipment, Power User, Software Development | Leave a Comment »

%d bloggers like this: