Bug 77 - libsigrok provides no means to provide the cause of an error.
Summary: libsigrok provides no means to provide the cause of an error.
Status: CONFIRMED
Alias: None
Product: libsigrok
Classification: Unclassified
Component: Other (show other bugs)
Version: unreleased development snapshot
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-14 09:52 CET by Joel Holdsworth
Modified: 2020-06-01 14:56 CEST (History)
1 user (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joel Holdsworth 2013-03-14 09:52:23 CET 
For example, on an FX2 device, doing 24MHz sampling with 16-bits is illegal, and the message will be printed to the command line, but there is no way for a GUI application to receive this information.
Comment 1 Gerhard Sittig 2020-06-01 14:56:33 CEST 
Does this still reproduce with recent versions? IIUC Pulseview now hooks into 
the library's logging, and users can lookup the cause behind "generic" errors 
in the log window. Granted it's not as obvious and "in your face", but available.

Does depend on library code to emit useful messages though, that's also true.