-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Itech IT8511A+ segmentation fault #35
Comments
With the pre-built x86_64 AppImage from https://github.com/knarfS/smuview/releases/tag/continuous the trace looks a bit different:
|
Compiling with
|
Could you please start SmuView with full log output and attach the whole output here? This is for connecting the load with the (factory) default serial settings (9600/8n1). Maybe you have to adapt the TTY:
When looking into the sigrok device driver, 38400 should be the maximum baud rate (not sure, I don't own that device):
|
Thanks for getting back to me, really appreciated. Just for the record, factory default setting on my unit is 115200 8N1. I've set it to 38400 though. Output with the version that was compiled with
|
The check when adding signals with other mq/mq_flags than specified in e.g. SourceSinkDevice to a fixed channel was defused in BaseChannel::add_signal() to prevent a subsequent segfault. This happens when sigrok drivers send unexpected mq/mq_flags (can be fixed in the sigrok driver), but also for AC power supplies and loads which is a design issue in SmuView right now that requires an API enhancement in libsigrok! With this fix, AC psu/loads will have two signals (DC and AC). Also add a Python test for fixed channels. Fixes issue #35.
Fixed :) Now signals can be added to "fixed" channels: ca7951b |
Thanks! Looks different now:
New builds can be found here: https://copr.fedorainfracloud.org/coprs/spike/sigrok/builds/ |
I've looked into this and I think the Itech driver (for whatever reason) returns a I've done some experimental changes in SmuView to catch this exception and output some error messages, which will hopefully help us to figure out the root issue. It would be great, if you would build my SmuView |
Sorry, only now got around to doing this:
I've built the 871df34 commit (which is the current head of the |
Describe the bug
Adding a new IT8511A+ device results in segmentation fault
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A new Itech 8511A+ device in the device tree
Screenshots or log
Clicking 'OK' in the screenshot above crashes smuview
Enviroment (please complete the following information):
Additional context
The libsigrok version
0.5.2-7.20210801gitb96051a
in the backtrace below is compiled from git commit sigrokproject/libsigrok@b96051a (can be found here: https://copr.fedorainfracloud.org/coprs/spike/sigrok/build/2356228/).The text was updated successfully, but these errors were encountered: