<dingwat>
would someone kindly remind me where ngsc stores configured instruments and other things? i.e. what do I need to delete to "reset"
<azonenberg>
dingwat: On linux that's normally ~/.config/ngscopeclient. under windows probably somewhere under appdata but i cant remember
<azonenberg>
there's three plain text files: recent.yml is recent instruments, recentfiles.yml is recent sessions, preferences.yml is settings
<dingwat>
ugh I hate windows search. Thankfully Everything exists. Windows is "AppData/Roaming/ngscopeclient"
<dingwat>
azonenberg: I'm running ngsc with --debug and can consistently provoke a crash, and I don't get any messages in the console. Is there an additional level of logging that I can enable?
<azonenberg>
dingwat: not globally. there's --trace but this is filtering by extra logging from a specific class since it's far too bloated to log everything
<azonenberg>
e.g. --trace TextureManager or --trace MainWindow
<azonenberg>
you can add as many --trace arguments as you want to trace a couple of glasses
<azonenberg>
classes*
<azonenberg>
otherwise if you get me a stack trace i can look int oit
<azonenberg>
do you have reproduction steps i can try on my end?
<dingwat>
Well, it might be specific to the agilent driver. Basically, when I connect to a scope in roll mode, I get a flood of messages 'Unknown trigger type "NONE"' which makes sense. But when I try to change the trigger to "Edge", it freezes and then crashes
<azonenberg>
then there's probably not going to be any useful trace output
<azonenberg>
my guess is that you're desyncing from the command stream
<azonenberg>
we don't currently support roll mode and i have no idea what the actual data transfer looks like there
<azonenberg>
but it's probably sending back data in a way that we don't understand and reading too few / too many samples
<azonenberg>
just a guess
<azonenberg>
but figure out where it crashes first
<dingwat>
hmm, now that I'm thinking about it, I'm guessing it's crashing because it's trying to set Edge trigger when the scope is in a state that Edge trigger cannot be set
<dingwat>
I should probably just not be in roll mode lol
<dingwat>
but a hard crash with no logs isn't ideal
<azonenberg>
i mean yes, that's obviously what's happening
<azonenberg>
the question is what the failure mode is and how can we error out cleanly rather than segfaulting :p
<dingwat>
yarp
<azonenberg>
Which will take more investigation
<dingwat>
much less importantly, windows cmd doesn't support ansi color sequences. sadge
<azonenberg>
At some point we can look at adding support for windows color stuff as a LogSink
<azonenberg>
I remember playing with it years ago, windows does have APIs for coloring in cmd.exe