[Xastir] Too many crashes

[Jack Twilley]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "James" =3D=3D James Washer <washer at trlp.com> writes:

James> I see know reason not to got the #ifdef route. Start with
James> linux, or whatever the most common platform and go from
James> there.

It is bad practice to attempt to #ifdef for specific operating
systems.  It is much more appropriate to use autoconf to detect
functionality and act on that detection.

James> When users report a core dump, they could include the data to
James> help support remote diagnosis.

This is already in place.  The most common cause of segfaults results
From=20that string which is included in the message.  Anything else can
be easily retrieved from the core file using tools like gdb.

James> For this type of event, additional debug data might be more
James> useful that a core, as (some) linux kernels to a pretty poor
James> job of dumping threaded apps.

This is a general fault of Linux, then, and not something that
applications should attempt to work around.

James> I've already offered to have the OP send me the core and
James> binary.. and I'll see what I can figure out.

Excellent!  I look forward to the results.

James>  - jim

Jack.
=2D --=20
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/28whGPFSfAB/ezgRAlkoAKDL2tgIrc+m8lKvbxRoFt4Fd3H5RQCfXx/6
SZtxNM+Jg5W5eWKrH0A/xeQ=3D
=3Dlyyx
=2D----END PGP SIGNATURE-----