Re: Console debugging under Windows
Re: Console debugging under Windows I tend to look up just about every question I have. That's how I came up with the --symfile thing in the first place. But no, that doesn't work, either. URL: https://forum.audiogames.net/post/584445/#p584445 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Console debugging under Windows
Re: Console debugging under Windows I tend to look up just about every question I have. That's how I came up with the --symfile thing in the first. But no, that doesn't work, either. URL: https://forum.audiogames.net/post/584445/#p584445 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Console debugging under Windows
Re: Console debugging under Windows I don't know how to load symbol files into lldb, have you just Googled it? I just use VSCode. But I know that it probably works, being as LLVM is behind the only high quality public documentation on the pdb format. URL: https://forum.audiogames.net/post/584233/#p584233 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Console debugging under Windows
Re: Console debugging under Windows Has anyone figured out how to load a PDB file into LLDB?My best guess is that it has to do with the --symfile parameter of "target create".BTW, I somehow managed to find the CDB debugger. In my start menu, there's something called Windows Kits or something. In there are a bunch of menu items like app verifier x64, debugging tools x64 or maybe WinDBG x64, anyway go to debugging tools x64 and do an open file location from the context menu. The resulting directory should contain cdb.exe. Your right this wasn't on my path either. URL: https://forum.audiogames.net/post/584220/#p584220 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Console debugging under Windows
Re: Console debugging under Windows @11Yeah I have no idea on the message box, but it's terrible and I hate it. First time I've had this issue, but Microsoft just lost a lot of powershell points because of this.For Python versions, there's two options. First is the launcher: on Windows you do py -3.6 arguments-here. That's included with Python but is kind of meh.What I do is install anaconda and let it manage them for me. I suspect that you'll not be able to find a workaround here, but you should really use virtualenvs for anything serious anyway, and anaconda will just let you:conda activate synthizerfrom anywhere. Unfortunately I always have to look up how to set a specific version when building new environments.you might be going "but that's overkill for multiversion python" and it is, but Anaconda also makes a shit ton of other Python stuff "just work" up to and including being able to install the Cuda SDK and other non-python deps transparently as needed, so if you're doing serious enough stuff that this matters you probably want it.Anyway I will have to learn lldb now that we have it working, heh. It should work pretty well, though. URL: https://forum.audiogames.net/post/576552/#p576552 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Console debugging under Windows
Re: Console debugging under Windows You are correct, sir. Can I change Powershell not to do that evil horrible thing to me ever again? It never occurred to me that a shell could suppress a dialog when there's clearly a GUI running that can show it. Linux will if there's no DISPLAY variable set to be fair, but just about everything that runs a GUI makes sure that is set.If there's a way to not install Python 3.6, I'd like that. I don't want to get into multi-Python-version hell and already have 3.8 installed.Thank you. URL: https://forum.audiogames.net/post/576114/#p576114 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Console debugging under Windows
Re: Console debugging under Windows Just figured out an lldb thing. Will follow up more later. Try running it under not Powershell, and see if it complains about python36.dll. Apparently powershell is suppressing a messagebox.If that's the case I may be able to get it working this weekend. It may just be as easy as installing Python 3.6. URL: https://forum.audiogames.net/post/576105/#p576105 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Console debugging under Windows
Re: Console debugging under Windows I hate the windows debuggers. Their commands are just so disgusting and weird. And I know what the crashing situation is like... I was trying to debug a crash in a QT app once but I couldn't because NVDA kept freezing on me every time CDB would freeze the thread when it crashed. I seriously have no idea why NVAccess hasn't fixed that bug yet (or found an alternative method of getting accessibility information that doesn't involve the embedding of a thread in every app that NVDA enters). URL: https://forum.audiogames.net/post/576096/#p576096 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Console debugging under Windows
Re: Console debugging under Windows @6Cdb is installed, but for some idiotic reason they don't put it on your path. You'll have to find it. It's been a while, or I'd quote the path for you: I've found the VSCode debugger so accessible and pleasant to use that, if I were in your situation, I'd sell my soul for it, so I've used it like all of once on Synthizer and otherwise haven't touched it since Libaudioverse.I'd love to know what's up with lldb too, though. If you find out, do tell. Someone should probably open an issue against them or something, just haven't needed it badly enough. URL: https://forum.audiogames.net/post/576057/#p576057 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Console debugging under Windows
Re: Console debugging under Windows @5Ah lovely, thanks. I just assumed it was my laptop. URL: https://forum.audiogames.net/post/576045/#p576045 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Console debugging under Windows
Re: Console debugging under Windows Here's my NVDA crasher not every half hour, sometimes multiple times in a 5-minute period. I'm basically hitting ctrl-alt-n on autopilot, almost doing it subconsciously at this point:https://github.com/nvaccess/nvda/issues/11591And yeah, I know about CBD, like I said, went through half a dozen Microsoft docs. Unless there's more to it than running "cdb" from a developer command prompt, it doesn't seem to be installed with the Win10 SDK like Microsoft says it should be.Anyway, through brute force stubbornness, I managed to make my component crash in a way that revealed a Rust backtrace. No closer to determining the root cause, other than the fact that the crash is no longer silent at least. Still frustrated by this debugger issue, though, and don't know why lldb is absolutely silent. URL: https://forum.audiogames.net/post/576017/#p576017 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Console debugging under Windows
Re: Console debugging under Windows @4VSCode lag introduced in NVDA 2020.2 is getting fixed in 2020.3. See this and the other things it links out to. URL: https://forum.audiogames.net/post/575996/#p575996 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Console debugging under Windows
Re: Console debugging under Windows Nope. Worst I can say with VSCode is that sometimes I press the up or down arrow key and braille shows the new line, while speech says the one I moved off.I'm sure that's more because this laptop is older than some of the programmers on this forum, and needs replacing.I'm sure there's some kind of psychosomatic thing that happens when switching to a new platform: You say how Linux is dead easy, and I've agreed with you when Ubuntu 6.10 rocked my world. These days, I get nothing but crashes and weirdness, same with OS X. Maybe it's because I expect them to fail? Maybe we should all go read up on the secret. It's not a problem of accessibility people, we're just not manifesting hard enough haha. URL: https://forum.audiogames.net/post/575983/#p575983 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Console debugging under Windows
Re: Console debugging under Windows Also, wait, just reread that, NVDA is freezing every half hour in VSCode? Don't have that problem, and don't know anyone else who does. URL: https://forum.audiogames.net/post/575980/#p575980 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Console debugging under Windows
Re: Console debugging under Windows When you installed debugging tools for windows, you also got a debugger called cdb with it, or should have. It's the command line equivalent of WinDBG. Docs here. You really want VSCode working if you can manage it because this thing is, let's go with decidedly unergonomic, but it works. Unfortunately it's been too long for me to remember commands, but I think the command for a backtrace is either k or kc. There's also a chm that'll open with .help if I recall, that'll give you all the commands and such, without having to dig around in Microsoft Docs.I think that if you grab launch.json from Synthizer and install the C/C++ extension, you can point it at whatever you need and it will work, irregardless of whether or not the files are C++. VSCode doesn't care about the files, mostly.your next frustration is likely to be that symbols on Windows aren't contained in the executable but instead in the .pdb produced when you build it. I just use VSCode's debugger so I don't remember precisely how to load them into other things. Sometimes it just works, sometimes you have to be explicit about "here is the symbol file". But you know it's a problem because you get meaningless backtraces if it's not loaded right. URL: https://forum.audiogames.net/post/575979/#p575979 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Console debugging under Windows
Console debugging under Windows Ugh, nothing has made me feel quite as stupid as has working with Windows for the past month. I'm trying to debug a crash in the Godot editor, and am looking for a console debugger. Or any accessible debugger, for that matter. I can't seem to get VSCode's integrated debugger to work because I don't see the C++ launch.json configuration entries the Microsoft docs claim I should. I suspect that's because I'm trying to debug the editor in the context of a game project, not a C++ project, so VSCode isn't showing these launch configurations. Maybe it should, and that's another bit of bullshit I have to sort out. But in the interest of working on my problem itself and not fighting to get there, I'm trying to just bring up the editor in a debugger and get a useful backtrace.I've tried WinDBG Preview, which is the only one I seem to be able to install and actually launch. Its accessibility is a bit...lacking.I tried lldb, which just silently fails. By which I mean "lldb", "lldb --help", etc. print absolutely nothing. I don't even think LLDB will work since the binary was built with MSVC, but it seems like it should at least give me some damn output.Supposedly there are half a dozen Windows debuggers, and I can't even get most of them to install. After running through a rabbit trail of MS docs, I learn that CDB is apparently part of the Windows 10 SDK. I had this installed already, but just did an update and can't find it. Searched c: for cdb, tried running it in the developer command prompt.I don't absolutely hate Windows. It's nice that I can run Steam and Itch mostly OK, and some of the apps are nice. But I'm about a week away from scrapping this experiment and switching back to Linux. It should *not* be this hard to launch a damn debugger, and lldb shouldn't just silently fail to do anything. I want to give this a shot and get good at it, but I've done computers for over 30 years, and I don't think Linux is just easier for me because I've run it since Slackware 96. When "apt-get install -y llvm gdb" get you debuggers that just work, well, there's something to be said for that, and that doesn't even touch on me having to restart NVDA half a dozen times per hour because something in VSCode locks up some speech synth watchdog thread. I'm trying to keep an open mind here, but how anyone gets anything done fighting with their systems this much slays me. URL: https://forum.audiogames.net/post/575973/#p575973 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
