Hi,
actually there should be the right rpath set in your executable. You
can check that like this:
bash$ readelf -a /local/scratch/usr/local/bin/wireshark |grep rpath
0x000f (RPATH) Library rpath:
[/local/scratch/usr/local/lib]
... if it looks much different something w
Yes I did, it traces back to libpcap_open invalid address
then I use ldd /local/scratch/usr/local/bin/wireshark (where my wireshark is
installed), it turns out
libwiretap.so.0 => /usr/lib/libwiretap.so.0 (0xb7f46000)
this is wrong, as I use ./configure --prefix=/local/scratch/usr/local, the
libwir
Hi,
Can you run Wireshark in DDD so you can get a backtrace?
See http://wiki.wireshark.org/Development/Tips
Thanx,
Jaap
yin sun wrote:
> Hello,
>
> I have compiled wireshark from 0.99.5 source on Suse10 Linux
> 2.6.16.27-0.9-smp x86. Initial launch is ok, change/save preference is
> ok, but f
Hello,
I have compiled wireshark from 0.99.5 source on Suse10 Linux
2.6.16.27-0.9-smp x86. Initial launch is ok, change/save preference is ok,
but failed at displaying packet with Segmentation fault. When I tried the
same pcap file with tshark, it is OK. So it must be some gui related
problem. Ca
