Why is "debug_dll.txt" Automatically Being Created?

[Hooovahh]

I'm losing my mind a bit and searching is failing me because of how internet search engines work.  So I have an application that listens over a TCP request.  The request will specify a path to a DLL it needs to run.  It will then run the DLL, and send back over TCP the results.  It is on a platform where the DLL is not compatible so this is a work around.

This all works fine in development.  I build an EXE, and it too runs as expected.  But one odd thing I noticed, is that after it runs the DLL and sends the reply over TCP, a new text file named debug_dll.txt is created next to the EXE.  In it appears to be the parameters being sent to the DLL, and the response coming back.  I looked at the code and I'm not explicitly doing this in the G code.  I added a disabled diagram structure around the Call Library function, built the new EXE, and now the text file isn't created, because the DLL isn't being ran.

I don't remember seeing this type of automatic DLL debugging built into the application before.  Is there some place I can turn this off?  The EXE will eventually be running from the Program Files folder where I probably don't have write permissions anyway but I just don't remember seeing this type of behavior, or where I could have accidentally set it.  Thanks.  LabVIEW 2020 32-bit, Window 10 x64.

[Gregory · Accepted solution]

Just to rule out the obvious, are you sure that the DLL isn't creating this file?

[Hooovahh]

Oh for Pete's sake. I've ran this DLL so many times I just assumed this wasn't it...turns out it is and it has always been ran from a location that didn't have write permissions so nothing happened. I ran it from the build directory and saw this.