https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14971
--- Comment #5 from Vasil Velichkov <vvvelich...@gmail.com> ---
(In reply to Peter Wu from comment #4)
> (In reply to Vasil Velichkov from comment #3)
> > I'm investigating some SCTP problems on a live platform but I'm not able to
> > share the pcap traces.
>
> Are the capture files large? Perhaps the capture is still being rescanned
> while the dialog is being loaded.
Yes they are pretty big, one of the captures is 49MB and contains 242922
packets.
> > > How easy is it for you to trigger the crash?
> >
> > Not easy at all, I had only 3 or 4 crashes during the several hours long
> > investigation.
>
> I thought it would be a memory corruption issue, but your valgrind trace
> should have complained in that case. So perhaps it is a race condition (I
> have not further investigated the cause).
Yes, a race condition sounds like a possible reason, I will try to run
wireshark under valgrind's helgrind and report any findings.
--
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
