Re: wireshark crash with segmentation fault

[Jeff Morriss <jeff.morriss.ws () gmail com>]

> /usr/lib64/libwireshark.so.2: undefined symbol: py_create_dissector_handle

Are you trying to run Wireshark from a build directory or after 
installing?  Are you installing to /usr/ or someplace else like /usr/local ?

The basic problem, I think, is that your Wireshark is compiled expecting 
the Python-scripting support to be enabled but your libwireshark (or at 
least the one in /usr/lib64) doesn't have it.  (FWIW the 
Python-scripting stuff is pretty broken so not enabling it is a wise thing.)

On 08/05/13 03:34, Hardik Patel wrote:
> Hi Jeff,
>
>
> Sorry for silly question as details is already there on website.
>
> i have attached error which i get on console and backtrace report with
> this email.
>
> Regards,
> Hardik Patel
>
>
> On Mon, Aug 5, 2013 at 9:04 AM, Hardik Patel <hardik.party () gmail com
> <mailto:hardik.party () gmail com>> wrote:
>
>
>
>     Hi Jeff,
>
>     I did not know how to take backtrace ?? can you please help me in
>     how to take it??
>
>
>     Regards,
>     Hardik Patel
>
>
>     On Fri, Aug 2, 2013 at 4:39 PM, Jeff Morriss
>     <jeff.morriss.ws () gmail com <mailto:jeff.morriss.ws () gmail com>> wrote:
>
>         On 08/02/13 08:54, Hardik Patel wrote:
>
>             Hi,
>
>             I come accross a problem in which some time wireshark crash
>             and i can
>             see "segmentation fault" on console.
>
>             i have created dissector in which i guess problem with tree
>             struct and
>             ett variables, i think i have not properly define.
>
>             I read that *The expansion of this node is controlled by the
>             |ett_foo|
>             variable.*
>
>
>             for example i click on packet frame which have long tree and
>             than i move
>             directly to packet frame which has smaller tree. so i guess
>             wireshark
>             remember that last time i have open 5th element of tree but
>             this time
>             packet frame do not have 5 element so it crash.
>
>
>         What's the backtrace when it crashes?  It seems quite unlikely
>         that this element expansion issue is the real cause.

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request () wireshark org?subject=unsubscribe