[Xastir] Too many crashes

[James Washer]

I see know reason not to got the #ifdef route. Start with linux, or whatever the most common platform and go from there. When users report a core dump, they could include the data to help support remote diagnosis. For this type of event, additional debug data might be more useful that a core, as (some) linux kernels to a pretty poor job of dumping threaded apps.

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

 - jim

On Sat, 13 Dec 2003 15:07:57 -0800 (PST)
"Curt Mills, WE7U" <archer at eskimo.com> wrote:

> On Sat, 13 Dec 2003, Jack Twilley wrote:
> 
> > If you can do that in such a way that it works on Solaris, FreeBSD,
> > and Cygwin as well as Linux, send me the patches and I'll test it.
> 
> Plus MacOSX.
> 
> 
> > If not, the current method of using operating-system-specific tools to
> > analyze core dumps left behind by segfaulting processes will probably
> > continue to be the standard approach to resolving these issues.
> 
> My first thoughts as well.  We could however put in #ifdef's for
> various operating systems, and improve each handler as people came up
> with patches.
> 
> I thought about creating a global string that each function writes to
> when you enter/exit the routine, but that'd be a lot of coding, and
> would slow Xastir down a bit with all the extra clutter.
> 
> -- 
> Curt, WE7U.				archer at eskimo.com
> http://www.eskimo.com/~archer
>   Lotto:  A tax on people who are bad at math. - unknown
> Windows:  Microsoft's tax on computer illiterates. - WE7U.
> The world DOES revolve around me:  I picked the coordinate system!"
> 
> _______________________________________________
> Xastir mailing list
> Xastir at xastir.org
> http://krypton.hscs.virginia.edu/mailman/listinfo/xastir
>