Bug 1424 - file with 8 channel data but 16 declared traces results in random data display
Summary: file with 8 channel data but 16 declared traces results in random data display
Status: CONFIRMED
Alias: None
Product: PulseView
Classification: Unclassified
Component: Data display (show other bugs)
Version: unreleased development snapshot
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-02 18:57 CEST by Gerhard Sittig
Modified: 2019-10-02 20:06 CEST (History)
0 users



Attachments
upper 16 channels with random content (which is not in the .sr input file) (22.56 KB, image/png)
2019-10-02 18:57 CEST, Gerhard Sittig
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gerhard Sittig 2019-10-02 18:57:40 CEST
Created attachment 547 [details]
upper 16 channels with random content (which is not in the .sr input file)

File gpib/serial/cbm1571/cbm_1571_read_status.sr comes with inconsistent 
metadata, although there is only logic data for 8 channels and unit size 
is 1, 16 channels are listed.  Which results in random data display which 
changes with zoom and pan (and may depend on the platform, compile options, 
etc).
Comment 1 Gerhard Sittig 2019-10-02 19:11:38 CEST
IRC discussion suggests the issue may result from not masking out absent data 
in the optimized code path for unaligned access.
Comment 2 Gerhard Sittig 2019-10-02 20:06:18 CEST
Strictly speaking the cbm_1571_read_status.sr file's metadata need not be 
inconsistent, but it seems to be unexpected, and is a good candidate to 
trigger the reported issue. :)  Is both the set of 16 channels, and the 
unitsize 1 and thus data availability for the first 8 channels only, available 
to the pulseview application code? So that traces' data can get masked out 
when their input data is absent?