[Help]Attach OllyDBG to CO?

[shimo diaz]

Well I am trying to attach OllyDBG to CO but it says access violation so how can I attach OllyDBG to CO?

[IAmHawtness]

Easiest and quickest way:
Options -> Exceptions -> "Ignore (pass to debugged program) following exceptions:" -> Tick the box that says "Memory access violations"

[shimo diaz]

Originally Posted by IAmHawtness

Easiest and quickest way:
Options -> Exceptions -> "Ignore (pass to debugged program) following exceptions:" -> Tick the box that says "Memory access violations"

Thanks but I heard that this may cause blue screen or screen crash, is that true?

[IAmHawtness]

Originally Posted by shimo diaz

Thanks but I heard that this may cause blue screen or screen crash, is that true?

Not very likely that making ollydbg ignore the exceptions would cause a blue screen. Actually, I'm 99.9998% certain that it won't cause a blue screen, unless of course your operating system doesn't support the EXCEPTION_NOT_HANDLED flag, which is very doubtful

[DarkMessiah]

Originally Posted by IAmHawtness

Easiest and quickest way:
Options -> Exceptions -> "Ignore (pass to debugged program) following exceptions:" -> Tick the box that says "Memory access violations"

options -> exceptions -> add last exception. that way it doesn't skip telling you if you have an error in a hooked function while you debug it

[shimo diaz]

Originally Posted by IAmHawtness

Not very likely that making ollydbg ignore the exceptions would cause a blue screen. Actually, I'm 99.9998% certain that it won't cause a blue screen, unless of course your operating system doesn't support the EXCEPTION_NOT_HANDLED flag, which is very doubtful

Anyway to find if my operating system supports the EXCEPTION_NOT_HANDLED flag or not?
I am running windows XP SP2 version 2002

Originally Posted by DarkMessiah

options -> exceptions -> add last exception. that way it doesn't skip telling you if you have an error in a hooked function while you debug it

Thanks btw congratulations on your website

[DarkMessiah]

Originally Posted by shimo diaz

Thanks btw congratulations on your website

thanks have to take a break til next thursday on adding everything that i want due to some traveling, but then after that im bout to flood it with the information i have

[IAmHawtness]

Originally Posted by DarkMessiah

options -> exceptions -> add last exception. that way it doesn't skip telling you if you have an error in a hooked function while you debug it

Yes it does, it says "Exception xxxxxxx - passed to program" or something similar in the buttom of the olly window

Edit:
Clicking the "Add current" to add the current exception is doing exactly the same as flagging the "Memory access violations" box since there's only one kind of memory access violation exception which is 0xC0000005

Originally Posted by shimo diaz

Anyway to find if my operating system supports the EXCEPTION_NOT_HANDLED flag or not?
I am running windows XP SP2 version 2002

Of course it supports it. All the current Windows support it, I was just thinking about emulators like WINE and such.

[DarkMessiah]

Originally Posted by IAmHawtness

Yes it does, it says "Exception xxxxxxx - passed to program" or something similar in the buttom of the olly window

Edit:
Clicking the "Add current" to add the current exception is doing exactly the same as flagging the "Memory access violations" box since there's only one kind of memory access violation exception which is 0xC0000005

The one's it has given me are

80000004 (SINGLE STEP)
C0000005 (ACCESS VIOLATION)
C0000008 (INVALID HANDLE)
C000001D (ILLEGAL INSTRUCTION)

so you might want to tick/add those as well

[IAmHawtness]

Originally Posted by DarkMessiah

The one's it has given me are

80000004 (SINGLE STEP)
C0000005 (ACCESS VIOLATION)
C0000008 (INVALID HANDLE)
C000001D (ILLEGAL INSTRUCTION)

so you might want to tick/add those as well

EXCEPTION_ACCESS_VIOLATION I understand, that's the thread from inside Conquer.exe that's causing those.
EXCEPTION_SINGLE_STEP is what you get when you put a hardware breakpoint somewhere inside the program and something is accessing that memory (executing, read/write, whatever the breakpoint is set to react to)
I have never experienced Conquer.exe throwing the other two exceptions though, that seems rather strange.

[DarkMessiah]

Originally Posted by IAmHawtness

EXCEPTION_ACCESS_VIOLATION I understand, that's the thread from inside Conquer.exe that's causing those.
EXCEPTION_SINGLE_STEP is what you get when you put a hardware breakpoint somewhere inside the program and something is accessing that memory (executing, read/write, whatever the breakpoint is set to react to)
I have never experienced Conquer.exe throwing the other two exceptions though, that seems rather strange.

it's tq. nothing is ever expected to throw normal errors

[mido2008]

thats a video of 5265-5269 CO client running on debugger (OllyDBG) and breakpoints works well.No crash,DC,BotJail,...
only made with client edits

that client is at Respected section in CodeXplosion forums