Bug 606 - Crash on removing decoder
Summary: Crash on removing decoder
Status: RESOLVED WORKSFORME
Alias: None
Product: PulseView
Classification: Unclassified
Component: Protocol decoding (show other bugs)
Version: unreleased development snapshot
Hardware: x86 Linux
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-15 22:02 CEST by bart
Modified: 2016-01-04 00:47 CET (History)
2 users (show)



Attachments
Screenshot of empty decoder stack (42.14 KB, image/png)
2015-07-15 22:02 CEST, bart
Details
gdb crash log (3.92 KB, text/plain)
2015-07-15 22:04 CEST, bart
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bart 2015-07-15 22:02:33 CEST
Created attachment 140 [details]
Screenshot of empty decoder stack

I can reproduce this bug in a few ways:

* Add Jitter decoder, and remove it
* Add UART decoder, and remove it. This leaves me with an empty decoder stack (see screenshot). Then I add the midi decoder, and remove it again.
* Add the UART decoder, and add the ARM ETMv3 decoder. Now remove UART
* Add the UART decoder, and add the ARM ETMv3 decoder. Now remove the ARM ETMv3 decoder.

This is not a complete list, I just wanted to show a few different examples. Most decoders clause a crash on their own (like Jitter), UART seems to be the exception.

I will add a GDB debug file.

Arch linux, all packages up to date.
Comment 1 bart 2015-07-15 22:04:08 CEST
Created attachment 141 [details]
gdb crash log
Comment 2 bart 2015-07-15 22:23:07 CEST
Found another crash situation:

* Add the UART decoder, load data from .sr file, remove UART decoder.
Comment 3 Uwe Hermann 2016-01-04 00:17:51 CET
Hm, I'm not able to reproduce any of these really, I think there must be some local library mixups or other strange issues going on. The operations mentioned work fine for various people on various OSes.

Only the last one "Add the UART decoder, load data from .sr file, remove UART decoder" was indeed a reproducible bug which is fixed in git now (#612).
Comment 4 Daniel Elstner 2016-01-04 00:47:46 CET
Wasn't there a bug like that caused by a specific version of Qt?