使用一个来自Cygwin的stackdump可执行文件 [英] Using a stackdump from Cygwin executable

问题描述

使用addr2line我可以知道程序是如何到达崩溃点的解码地址一个。有没有替代工具，可以缓解使用堆栈转储调试？
是否有办法在Insight / Gdb中加载此信息？

解决方案

您可以指示Cygwin启动gdb调试器只是在发生故障的时候。
为此，请将 error_start = action 添加到Cygwin环境变量：

export CYGWIN =$ CYGWIN error_start = gdb -nw％1％2

否则可以让Cygwin生成一个真正的核心转储。

export CYGWIN =$ CYGWIN error_start = dumper -d％1％2

So I wrote buggy code that occasionally crash ... and creates a stackdump file.

Using addr2line I can figure out how the program got to the crash point by decoding the addresses on by one. Is there an alternative tool that can ease the debug using stack dumps? Is there a way to to load this information in Insight/Gdb?

解决方案

You can instruct Cygwin to start your gdb debugger just in time when an fault occurs. To achieve this, add error_start=action to the Cygwin environment variable:
export CYGWIN="$CYGWIN error_start=gdb -nw %1 %2"

Else you can have Cygwin generate a real core dump.
export CYGWIN="$CYGWIN error_start=dumper -d %1 %2"

这篇关于使用一个来自Cygwin的stackdump可执行文件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！