Description of problem:
Wireshark was reported to crash due after triggering a debug trap when
attempting to dissect iSeries traffic.
Version-Release number of selected component (if applicable):
This is fixed in upstream revision 21034.
I was not able to reproduce this on an x86_64 architecture box, nor have I
tried on i386. Moreover I can not imagine a situation when a bug would result
into getting a TRAP signal other than careful and targeted explotation -- but
as this is not the case I am probably missing something.
Created attachment 158200 [details]
Capture file of iSeries traffic that was reported to crash Wireshark
This issue was addressed in:
Red Hat Enterprise Linux:
Reporter changed to firstname.lastname@example.org by request of Jay Turner.