[Xastir] Too many crashes

[Jack Twilley]

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

>>>>> "Curt" =3D=3D Curt Mills <Curt> writes:

Jack> If you can do that in such a way that it works on Solaris,
Jack> FreeBSD, and Cygwin as well as Linux, send me the patches and
Jack> I'll test it.

Curt> Plus MacOSX.

Yeah, that too.

Jack> If not, the current method of using operating-system-specific
Jack> tools to analyze core dumps left behind by segfaulting processes
Jack> will probably continue to be the standard approach to resolving
Jack> these issues.

Curt> My first thoughts as well.  We could however put in #ifdef's for
Curt> various operating systems, and improve each handler as people
Curt> came up with patches.

Testing for operating systems makes autoconf cry.  Testing for
functionality is a better way to do it, but I still say our current
system works fine.

Curt> I thought about creating a global string that each function
Curt> writes to when you enter/exit the routine, but that'd be a lot
Curt> of coding, and would slow Xastir down a bit with all the extra
Curt> clutter.

That would be pretty messy, I agree.

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/25KSGPFSfAB/ezgRAvmbAKCp2E1ZziSv/3RnFSj92zPI8RFu7gCcCl6L
79hK4194Q5MJkvMyDsM32rs=3D
=3DugbX
=2D----END PGP SIGNATURE-----