On Wed, 25 May 2011, Derek Gaston wrote:

> I like the idea of adding a handler for segfaults that writes a
> stack trace!  Especially if it overrides the Petsc error handlers.
> It wouldn't be helpful in this particular case because I already got
> the stack trace with a core dump... but it would be helpful in
> general in the future.

Can you copy the stack trace here?  Obfuscate application-level
function names if need be.  I'd also be curious to know how many
processors the segfault occurs on.
---
Roy

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to