Wireshark-bugs: [Wireshark-bugs] [Bug 11839] Starting Wireshark from Visual Studio 2013 gives Sy

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 01 Dec 2015 15:22:59 +0000

changed bug 11839


What Removed Added
Status UNCONFIRMED CONFIRMED
Ever confirmed   1

Comment # 2 on bug 11839 from 
(In reply to Pascal Quantin from comment #1)
> I believe this is already addressed by Graham in
> https://code.wireshark.org/review/#/c/12117/

Partially, as I noted there the change I made only seems to fix the issue when
running in the Visual Studio Debugger, but at least that was a step forward.

There's something odd about the DLL search order that doesn't seem to accept
the addition of the run\xxx directory to PATH (except when run under the
debugger) when spawning the extcap processes.

The (temporary) workaround for the moment is to manually add that directory to
the PATH env var in the shell you're running Wireshark from.

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