seg fault produces stackdump with no stack trace

[Dave Korn]

Steve Waldo wrote on 01 August 2008 16:24:

> When my app gets a seg fault it produces the expected stackdump file:
> 
> [1]-  Segmentation fault      (core dumped) ./ResourceMgr
> 
> but the resulting file contains no stack trace:

> Is there a setting I'm missing somewhere? 

  Nah, it probably just means the stack was too badly trashed to backtrace
successfully.  You're probably best off trying it under gdb.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/