Re: [fltk.general] help with debugging a segv?

[MacArthur, Ian (SELEX GALILEO, UK)]

> what other infos would i get if it was linked against the 
> debug libs? ty,

With the debug lib, it makes it easier to (via symbol names) query the
value of variables and so forth at the break point, e.g. you can do

> p widget

(P == print value of)

And it will print the current value of "widget", so you can look for
NULL pointers or incorrect variables an etc.

However, I see that you are linking to fltk dynamically; To investigate
this problem, I would first switch to static linking, at least for fltk
and the other small libs (portmidi and porttime I always static link,
they are so tiny and it can save a lot of hassle) as this removes any
ambiguity about which version is being loaded and so forth, and makes it
much easier to determine at link time if there are any missing symbols
or not.

Once you have the static linked version playing nice, then try the
dynamic linked version again...



SELEX Sensors and Airborne Systems Limited
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 
3EL
A company registered in England & Wales.  Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

_______________________________________________
fltk mailing list
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk