Wireshark-bugs: [Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after inst
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 15 Sep 2016 11:56:39 +0000

Comment # 22 on bug 12845 from 
(In reply to Roland Knall from comment #21)
> There seems to be multiple issues. I have an utility here, which has an
> issue if more than 9 parameters exist for an interface, together with
> parameters of a certain depth.
> 
> I am currently looking into it, but this bug is confirmed.

I've been looking into this together with a colleague. It get's stranger every
minute. We've been able to narrow it down a little bit further. From what I can
deduce, it appears that due to the excessive number of printf's, that create
the output, an internal buffer overflows - producing a deadlock. Basically
Windows is waiting for someone to collect on the printfs and is holding the
output in the meantime. 

If anyone has an idea on how to change this behaviour, I am open to it. The
only other option I do have is to replace the extcap_spawn_sync calls to
extcap_spawn_async calls with a waiting for the utility to end. As I have
currently something else on my plate, this will take a while for me to fix, so
anyone who wants it, feel free to do it.

You are receiving this mail because:
  • You are watching all bug changes.