When to use assembly language to debug a c / C ++ program?

Question

When to use assembly to debug a c / C ++ program?

Does this assembly help debug programs?

Answer 1

This can be very useful in cases where you cannot (yet) reliably reproduce the error, for example, due to damage to the heap / stack. You can get one or two dump cores, quite possibly from a client. Even if your debugger is reliable, looking at the assembly, it can tell you exactly which instruction (and, therefore, what part of the memory is corrupted).

, ( ) . , / .. , , . diassembly.

/ , , . , , , , .

Answer 2

"", C/++, , ... asm, .

ASM C... , .

x86!

Answer 3

, . , .

C/++, C/++, .

Answer 4

, , , C/++.

, , , . , , . -, , .

, , - . , .

Wiki .

Answer 5

. GCC .

. GCC 2.95 3.4.3, , .

, , . , , , , 16- 32- .

, , - , "" . , , , , , - .

Answer 6

, . - , , . , .

- http://mohit.io/blog/assembly-and-the-art-of-debugging/

Update → , . http://mohit.io/blog/debugging-modifying-code-at-runtime/

Answer 7

, , " ". ( , ), , , . , , , .

Answer 8

, gcc . - "" gcc , .

/* global */
int x = 1;

void *myFunc() {
    /* do something productive */
    x = 0;
    return NULL;
} 

int main() {
    thread_create(myFunc);

    while(x) continue;

    exit(1);
}

while(x) continue; jmp 0xDEADBEEF ( 0xDEADBEEF - jmp). , x .

-.

Answer 9

, . , , , , , .

Answer 10

, , . , , , . - ALT-6. , .

Answer 11

; , minidump . , , ( ).

Answer 12

I have some benefit for my build skills looking for bugs that were caused by the new version of the compiler being used. But compiler errors are very rare, so my answer will not be for debugging.

It is interesting to see how the compiler solves the build problem from your source, but this is by no means debugging.