I use named pipes to access serial port data. After I upgraded from Wireshark 1.6.4 to Wireshark 1.6.6, I get a runtime error when I try to enter my named pipe address in the capture dialog box. asked 05 Apr '12, 10:08  korwinula |
One Answer:
Hmm, a problem having to do with named pipes was supposed to have been fixed with 1.6.6. You might want to try 1.6.7 just in case, but if that doesn't work, I'd suggest you open a bug report. Or try/use the development version (e.g., 1.7.1). answered 27 Apr '12, 08:03  JeffMorriss ♦ |
I downgraded to 1.6.4 and wireshark is now crash free after a few hours of solid running