Bug 77

Summary:	libsigrok provides no means to provide the cause of an error.
Product:	libsigrok	Reporter:	Joel Holdsworth <joel>
Component:	Other	Assignee:	Nobody <nobody>
Status:	CONFIRMED ---
Severity:	normal	CC:	Gerhard.Sittig
Priority:	Normal
Version:	unreleased development snapshot
Target Milestone:	---
Hardware:	All
OS:	All

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.