azonenberg changed the topic of #scopehal to: ngscopeclient, libscopehal, and libscopeprotocols development and testing | https://github.com/ngscopeclient/scopehal-apps | Logs: https://libera.irclog.whitequark.org/scopehal
<_whitenotifier-f> [scopehal-apps] yoofie starred scopehal-apps - https://github.com/yoofie
<d1b2> <fpga_zealot> For a windows segfault, what information do you want?
<_whitenotifier-f> [scopehal] azonenberg pushed 1 commit to master [+0/-0/±1] https://github.com/ngscopeclient/scopehal/compare/884314873a83...9753ecd2a453
<_whitenotifier-f> [scopehal] azonenberg 9753ecd - Added missing check for digital channel size
<d1b2> <fpga_zealot> @azonenberg What Flags? what Log files should I add to the report?
<d1b2> <azonenberg> @fpga_zealot default for troubleshooting is to do a debug build (CMAKE_BUILD_TYPE=DEBUG) to get full symbols etc
<d1b2> <azonenberg> and report a stack trace of the crash if applicable
<d1b2> <azonenberg> plus the result of running the application with --debug
<d1b2> <fpga_zealot> k will do
<d1b2> <azonenberg> (we should probably make a crash reporting guide at some point)
<d1b2> <azonenberg> we may or may not want full scpi command logging but that depends on what the initial investigation shows
<d1b2> <azonenberg> it's too verbose to do by default in most cases
<d1b2> <johnsel> I think that would be useful
<d1b2> <johnsel> Also for driver writing
<d1b2> <johnsel> Maybe make a seperate task list for things like this
<d1b2> <johnsel> I think there are people more than happy to write such things but it gets lost between regular tickets/issues
<d1b2> <azonenberg> its just a matter of staffing resources. I don't have the time to write everything that needs doing
<d1b2> <johnsel> ok well you typed it now
<d1b2> <azonenberg> i had a potential ping on mastodon from an interesting technical writer
<d1b2> <azonenberg> interested*
<d1b2> <azonenberg> but havent heard back from them
<d1b2> <johnsel> if you add to it "john make list for that" I am always happy to lend a quick hand
<d1b2> <azonenberg> ok when i get a chance i'll try and come up with some kind of documentation wishlist and maybe file tickets against scopehal-docs for them or something
<d1b2> <johnsel> Alright I'm not a great write but I can try to spend half an hour per week on it or so
<d1b2> <johnsel> But I think we have more people interested in such work if we can point them to it
Degi_ has joined #scopehal
Degi has quit [Ping timeout: 260 seconds]
Degi_ is now known as Degi
veegee has quit [Remote host closed the connection]
veegee has joined #scopehal
bvernoux has joined #scopehal
bvernoux has quit [Quit: Leaving]
azonenberg has quit [Ping timeout: 256 seconds]
sorear has quit [Read error: Connection reset by peer]
elms_ has joined #scopehal
_whitenotifier-f has quit [Ping timeout: 268 seconds]
sorear has joined #scopehal
elms has quit [Ping timeout: 268 seconds]
elms_ is now known as elms
anuejn has quit [Remote host closed the connection]
vup has quit [Ping timeout: 255 seconds]
azonenberg has joined #scopehal
vup has joined #scopehal
anuejn has joined #scopehal