I wanted to do some work on lzbacon (D port of lzham-codec with some extras such as tarball support), but without a debugger it's pretty hard (I suspect an error in the multithreading when looking up for a value, or some C++ language quirk I missed). The current state of mago-mi is nearly unusable with very limited command support, and I don't want to go back to VisualD after VSCode for either a usable mago or VS native debug. I couldn't find LLDB on my harddrive anymore, and GDB needs DWARF symbols.

Then I had a thought: Is there anything usable on the market besides these?

After I a quick Google search, I encountered with the "guy she told you to not to worry about":

https://x64dbg.com/#start

It seems it needs *.pdb files for symbols, which I'll test tomorrow, hopefully I don't have to cook something complicated for my family to waste my time. While I'm still encouraged to improve mago instead (I think alternatives are always a good option and the conversion will be finished by the weekend), maybe it'll be useful for some. Maybe I can use it for mago too.

On Wednesday, 3 October 2018 at 03:25:04 UTC, solidstate1991 wrote:
> https://x64dbg.com/#start

I've tried it. It's not very good for source-level debugging. Seems to be primarily aimed at reverse-engineering / debugging programs you don't have the source for.

On Wednesday, 3 October 2018 at 03:25:04 UTC, solidstate1991 wrote:
> and I don't want to go back to VisualD after VSCode for either a usable mago or VS native debug.

Visual Studio makes a decent stand-alone source-level debugger. Just select the .exe file, and right-click it in the project/solution pane to start a debugging session. (Of course, you need to build with -m32mscoff or -m64 as well as -g). VisualD isn't even needed, though VS by itself won't understand D types like arrays/strings.

On Wednesday, 3 October 2018 at 03:25:04 UTC, solidstate1991 wrote:
> Then I had a thought: Is there anything usable on the market besides these?

It may not be enough for your needs, but VSCode C++ debugger somewhat works for D. I can't set breakpoints, but stepping through code works and watches also work for most simple types.

On Wednesday, 3 October 2018 at 13:20:03 UTC, JN wrote:
> On Wednesday, 3 October 2018 at 03:25:04 UTC, solidstate1991 wrote:
>> Then I had a thought: Is there anything usable on the market besides these?
>
> It may not be enough for your needs, but VSCode C++ debugger somewhat works for D. I can't set breakpoints, but stepping through code works and watches also work for most simple types.

Enable the setting in your user/workspace:

  // Allow setting breakpoints in any file.
  "debug.allowBreakpointsEverywhere": true,

On Wednesday, 3 October 2018 at 23:51:38 UTC, tide wrote:
> On Wednesday, 3 October 2018 at 13:20:03 UTC, JN wrote:
>> On Wednesday, 3 October 2018 at 03:25:04 UTC, solidstate1991 wrote:
>>> Then I had a thought: Is there anything usable on the market besides these?
>>
>> It may not be enough for your needs, but VSCode C++ debugger somewhat works for D. I can't set breakpoints, but stepping through code works and watches also work for most simple types.
>
> Enable the setting in your user/workspace:
>
>   // Allow setting breakpoints in any file.
>   "debug.allowBreakpointsEverywhere": true,

I'll give it a try.

Stuff like that should be added to Debuggers wiki I guess. Right now it's full of some outdated out-of-IDE debuggers that barely anyone uses nowadays.

On Wednesday, 3 October 2018 at 13:08:50 UTC, Vladimir Panteleev wrote:
> On Wednesday, 3 October 2018 at 03:25:04 UTC, solidstate1991 wrote:
>> and I don't want to go back to VisualD after VSCode for either a usable mago or VS native debug.
>
> Visual Studio makes a decent stand-alone source-level debugger. Just select the .exe file, and right-click it in the project/solution pane to start a debugging session. (Of course, you need to build with -m32mscoff or -m64 as well as -g). VisualD isn't even needed, though VS by itself won't understand D types like arrays/strings.

I cannot find that option...

On 21/10/2018 5:59 PM, solidstate1991 wrote:
> On Wednesday, 3 October 2018 at 13:08:50 UTC, Vladimir Panteleev wrote:
>> On Wednesday, 3 October 2018 at 03:25:04 UTC, solidstate1991 wrote:
>>> and I don't want to go back to VisualD after VSCode for either a usable mago or VS native debug.
>>
>> Visual Studio makes a decent stand-alone source-level debugger. Just select the .exe file, and right-click it in the project/solution pane to start a debugging session. (Of course, you need to build with -m32mscoff or -m64 as well as -g). VisualD isn't even needed, though VS by itself won't understand D types like arrays/strings.
> 
> I cannot find that option...

Open it as a solution/project if I remember right.