On 18/09/2019 19:55, Random D user wrote: > On Wednesday, 18 September 2019 at 07:30:21 UTC, Rainer Schuetze wrote: >> >> >> On 15/09/2019 20:11, Random D user wrote: >>> I've been trying to set thread names for debugging, but it seems Mago >>> just ignores all names. >> >> SetThreadDescription works for me (in VS2019). >> >> If you are using the visualdproj project, do not use "Mago" as the >> debugger, the "Visual Studio" debugger work better and have D support >> through a mago based expression evaluator extension. > > Yes, I'm using VS2019. > Interesting. I indeed have been using Mago (pretty old project files too). > I did not know that "Mago" was the wrong debugger to use. I think it > used to be so that it was the preferred and more feature complete (i.e. > correct) debugger. It was preferred before the debugger extension existed (2017), and the latter only works for VS2012 and later (unlikely to be an issue now). I guess I should add that info to the combo box somehow. > > Thanks. > And what it's worth, I think you're doing high value work with Visual D, > much appreciated. > Thanks.
Re: Thread names in Visual Studio and Mago
Rainer Schuetze via Digitalmars-d-debugger Fri, 20 Sep 2019 00:21:47 -0700
- Thread names in Visual Studio a... Random D user via Digitalmars-d-debugger
- Re: Thread names in Visual... Rainer Schuetze via Digitalmars-d-debugger
- Re: Thread names in Vi... Random D user via Digitalmars-d-debugger
- Re: Thread names i... Rainer Schuetze via Digitalmars-d-debugger
