On Thu, 2020-10-22 at 18:49 +0200, sdbbs wrote:
>
> Note that this .vcd file has a line like `$scope module
> libsigrok $end` or similar, which will cause sigrok to print
> this, if you try loading that .vcd file:
>
> >sr: input/vcd: Skipping scope with application's package name:
> >libsigrok
>
> ... so, I had to change that line to `$scope module top $end`.
Out of curiousity: Why do you _have_ to change that line? IIUC
the message does not show up by default, only at manually raised
log levels. Where it's shown for information, but is far from
fatal or anything to worry about.
> However, if I then start a new PulseView session (PulseView
> 0.5.0-git-9d307c6, libsigrok 0.6.0-git-d7df9dc/4:0:0 (rt:
> 0.6.0-git-d7df9dc/4:0:0) on Windows 10), and I try importing
> this stereo.vcd, then PulseView just shuts down, without any
> error messages.
Out of interest: Did your platform not show the SIGFPE or similar
error cause that I got here when I tried?
The previous implementation was flawed in the case of analog-only
data. Total absence of logic data resulted in a division by zero.
This got fixed in libsigrok 2cb4204c6f31. Will be part of the
next nightly build.
> I also tried opening the .vcd in sigrok-cli with the intent of
> exporting .sr from there - log messages indicate that the .vcd
> file is parsed by sigrok-cli, however the output .sr file is
> never created.
Same cause. Because file format support is implemented in the
library which is shared by all applications. Behaviour should be
the same across all of them.
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
ask your parents or an adult to help you.
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
