tags:

views:

25

answers:

0
Q: 

If program crashes from within cygwin, the post mortem debugger does not trigger

Running a (seg)faulty native windows binary from within a cygwin shell leads to restart the binary for several times. Since I want to analyze the bug I activated windbg as the post mortem debugger (yes, as administrator), but somehow cygwin interferes and windbg does not get triggered.

OS: 64bit Windows7 (happened on WindowsXP as well), Cygwin 1.7.x

related questions

Lost use of forward slash in windows command prompt
What's the bare minimum Cygwin install to have DDD running properly on XP?
How do I use cygwin behind the corporate firewall
How Can I Build wxWidgets With Eclipse On Windows
grep: matching on literal "+"
Why does GCC-Windows depend on cygwin?
Mount floppy image in cygwin
Connect to SQL Server from cygwin window times out, from DOS prompt works
best ways to use cygwin
Does the tee command always wait for EOF?
Rsync on Windows - Socket operation on non-socket
How can I associate .sh files with Cygwin?
How to optimize compiling a 32 bit application in Visual C++ 2005 on a 64 bit windows sever 2008
Using `pkg-config` as command line argument under cygwin/msys bash
How do I change the colors displayed in cygwin rxvt?
Renaming/Mapping Cygwin Folders
Using Component Object Model (COM) on non-Microsoft platforms
Tools for command line file parsing in cygwin.
VS2008 Command Prompt + Cygwin
msys vs cygwin
Objective C for Windows
Are there any resources for becoming a Cygwin "power user"?
How do I execute a file in Cygwin?
Why does Vista complain about a dead process when I use Cygwin X11 ssh and how do I get it to shut up?
Starting off with OpenGL under Cygwin