Hi all,
I am writing a new dissector and for that purpose, have written a new
file. As suggested by Jeff, i have included the file in Makefile.commom
also for compilation to be successful.
But, when trying to capture the packet i am getting this error.
*ERROR:packet.c:1982:call_dissector_only:
Hi folks,
libtool is getting in the way and the result is that shared objects
are not found or I have to set up a long LD_LIBRARY_PATH
Is there a simpler way?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___
Sent via:
Hi Richard,
2012/5/13 Richard Sharpe realrichardsha...@gmail.com:
Hi folks,
libtool is getting in the way and the result is that shared objects
are not found or I have to set up a long LD_LIBRARY_PATH
Is there a simpler way?
You need to run Wireshark with the following command line:
Am 13.05.2012 07:59, schrieb Krishnamurthy Mayya:
But, when trying to capture the packet i am getting this error.
*ERROR:packet.c:1982:call_dissector_only: assertion failed: (handle != NULL)
*
*Aborted*
Any idea what might have gone wrong ???
call_dissector_only is called from call_dissector
On Sat, May 12, 2012 at 11:39:11PM -0700, Richard Sharpe wrote:
Attached is a set of patches that seems to do the trick.
[...]
It would be useful if people could review them ...
This patch is too big for me, it'd be great if this patch could be splited.
But some notes:
1/ hdr, hdr_size in
This is a topic that's been stewing in the back of my brain for a
while now, but it's cooked enough that I think it's worth getting
feedback on. This is a long, (overly) detailed email - read with
caution :)
tl;dr; I think it's possible to support parallelized (multi-threaded)
packet dissection
Try:
libtool --mode=execute gdb ./tshark
This can be used for gdb, ddd, kdbg, etc.
If I am trying to fix a dissector, I use tshark. Easier to watch in debugger
and the GUI dose not get in the way
--- On Sun, 5/13/12, Richard Sharpe realrichardsha...@gmail.com wrote:
From: Richard Sharpe
On Sun, May 13, 2012 at 10:33:56AM -0400, Evan Huus wrote:
Please ask questions and provide feedback, I'm sure there are things
I've missed.
Thoughts?
Sounds too complicated for me :)
I've always wanted to write some PoC for multithreaded wireshark,
but something simpler, like
On Sat, May 12, 2012 at 04:10:49PM -0700, Guy Harris wrote:
On May 12, 2012, at 12:43 PM, Jakub Zawadzki wrote:
Do we really need to capture from pipes in dumpcap?
I believe the ability to capture from a pipe was introduced in order to
handle capturing from sources that libpcap/WinPcap
