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
Degi_ has joined #scopehal
Degi has quit [Ping timeout: 248 seconds]
Degi_ is now known as Degi
balrog has joined #scopehal
bvernoux has joined #scopehal
bvernoux has quit [Read error: Connection reset by peer]
<dingwat> I'm still unable to build ngscopeclient on some Windows systems and I don't know if it's a compiler bug or not...
<dingwat> trying to understand if it's related to this bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107986
<d1b2> <johnsel> is it related to the msys/compiler versions?
<azonenberg> dingwat: that issue has come and gone for a while and i dont think there's been any resolution on our end
<azonenberg> some people get hit by it some dont
<azonenberg> we think its a compiler bug given the context, i dont think its an actual out-of-bounds error
<dingwat> i wonder if i can try forcing different gcc versions
<d1b2> <hansemro> dingwat: can you share list of installed msys2 packages (pacman -Q)?
<dingwat> hansemro, I did a pacman -Syuu and updated my packages (gcc did not get upgraded, notably) and I'm rebuilding... in the meantime, here's pacman -Q output: https://paste.mozilla.org/incM0TCt
<dingwat> FWIW, I installed msys2 on this machine specifically to build ngscopeclient, so there shouldn't be any extraneous packages
<dingwat> ok, confirmed it still fails with the array-bounds error, with msys2 packages upgraded and the latest commit on master checked out
<d1b2> <hansemro> With updated packages, I am now getting the same error, so at least I can reproduce it for now.
<dingwat> hansemro, were you on an older version of gcc previously?
<d1b2> <david.rysk> Probably need to suppress some more errors
<d1b2> <hansemro> dingwat: will check soon
<dingwat> well, it's not the most graceful workaround, but I can confirm that throwing a #pragma GCC diagnostic ignored "-Warray-bounds" around SiglentSCPIOscilloscope::AcquireData() does allow compilation to succeed
<dingwat> I'm guessing "Waveform preamble length (1000) does not match data length (0)" means we expected the scope to send 1k samples and it sent zero? I'm crashing with that message pretty frequently
<azonenberg> dingwat: yes that is correct
<azonenberg> it shouldnt crash, we should be able to at least add code to cleanly exit the acquisition when that happens
<azonenberg> but generally speaking once your communication with the scope desyncs all bets are off
<dingwat> gotcha
<dingwat> azonenberg: also fwiw, tek responded to my inquiry about ngscopeclient, and said, and I quote "We have great relations with the developer of this tool. In fact we have an HSI enabled scope with him right now." XD