OllyDbg无法调试Visual Studio exe [英] OllyDbg can't debug visual studio exe

查看:305
本文介绍了OllyDbg无法调试Visual Studio exe的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我刚刚用以下简单代码创建了一个新的vc ++ exe:

I've just created a new vc++ exe with this simple code:

#include<stdio.h>
#include<string.h>
#include<windows.h>

int ExceptionHandler(void);
int main(int argc,char *argv[]){

char temp[512];

printf("Application launched");

try 
{

  throw "error";

} 
catch (... )
{
    ExceptionHandler();
}
return 0;
}
int ExceptionHandler(void)
{
    printf("Exception");
    return 0;
}

该应用程序非常简单,并且创建了一个依赖kernel32.dll和MSVCR100D.dll的exe文件.

The app is extremely simple, and an exe file depending on kernel32.dll and MSVCR100D.dll is created.

当我尝试将其导入并调试到OllyDbg中时(我只想在堆栈窗口中看到SEH链),它说模块'testseh'在代码外具有入口点(如PE标头中所指定).也许该文件是自解压缩或自修改的.设置断点时请记住它!"而且没有执行任何代码,它直接跳到ntdll.dll崩溃部分(实际上exe崩溃了,但我无法逐步执行printf指令)

When I try to import and debug it into OllyDbg (I just wanted to see the SEH chain in the stack window) it says "Module 'testseh' has entry point outside the code (as specified in the PE header). Maybe this file is self-extracting or self-modifying. Please keep it in mind when setting breakpoints!" and no code is executed, it jumps directly to the ntdll.dll crash part (in fact the exe is crashing but I can't step by step the printf instructions)

这种行为如何产生? exe既不依赖CLI,也不依赖CLR,我是否缺少某些东西?

How come this behaviour? The exe doesn't rely on CLI neither CLR, am I missing something?

推荐答案

从olly处获取的编译器异常很重要(错误的设置)

Compiler exceptions taken from olly as critical (wrong settings)

这篇关于OllyDbg无法调试Visual Studio exe的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆