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
0x000000000000000f (RPATH) Library rpath:
[/local/scratch/usr/local/lib]
... if it looks much different something wrong happened.
Then try to do something like:
bash$ LD_LIBRARY_PATH=/local/scratch/usr/local/lib:$LD_LIBRARY_PATH \
ldd /local/scratch/usr/local/bin/wireshark
... does it still show the wrong lib? If not it might help you to
export the LD_LIBRARY_PATH like this. This for sure does not solve the
root of your problem - whatever this is.
HTH,
Martin
On 6/18/07, yin sun <sunyin51@xxxxxxxxx> wrote:
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 libwiretap should
points to /local/scratch/usr/local/lib/libwiretap.so.0
right?
How to fix this?
Thanks,
/Yin
On 6/18/07, Jaap Keuter <jaap.keuter@xxxxxxxxx> wrote:
> 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 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. Can someone help me on this. How to proceed to find the
> > problem.
> >
> > Thanks,
> > /Yin
> >
>
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev
