About the GDB Debugger

0

Oops, I wanted to get in touch with you.

I run my application with the GDB debugger, I'm not very knowledgeable about it, but from what I know it's one of the best. The fact is that in some cases it reports the error but not clearly, since my application has loops and pointers. I would like to know if you can read a memory address and get the class data.

0x00000000004f36ae in Container::~Container (this=this@entry=0x7ffef0793bd0, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at container.cpp:58

In this case, for example, I'd like to access the address 0x7ffef0793bd0 of the container class, and then get the variables that caused the problem.

    
asked by anonymous 29.11.2018 / 18:38

0 answers