stuck and get a blank display on centos7

[caicaixuehua]

On centos7,the edb will stuck and the gui is blank,I don't know why.
the stucked line:

stucked gui:

[caicaixuehua]

If I debug 32bit mode,it will not be stucked. If I debug 64bit mode,it will be stucked.What happened?

[caicaixuehua]

Debug 32bit mode program,edb also may be stucked.

[caicaixuehua]

When the gui is blank, botton of step into,step over is okay(the registers panel is okay and display rightly). Step out has the following error:

[10110111]

I think EDB doesn't support debugging across execve system call, which your screenshot is showing.

[caicaixuehua]

Okay.But it is always in ld-2.17.so when I step over. Not enough step over?

[10110111]

Of course, from _start to __libc_start_main to main you'd have to step quite a lot of steps if you do it manually. You should put a breakpoint at main or whatever you have, and run the process, as you normally do at the beginning of your debug sessions.

[caicaixuehua]

But how to find the main entry point?

[10110111]

Apparently, EDB doesn't support this case well. In particular, it can't set breakpoints after execve or modify memory in any other way, so you're out of luck here.

The only suggestion I have is to start the new process manually in a separate debugging session with appropriate parameters and environment (this might not work if it relies on inherited descriptors, but well). Then Function Finder can find main, you can set a breakpoint there etc.

[caicaixuehua]

Yes,it can't set breakpoints after execve.Okay, I know,thank you very much.

[10110111]

@eteran
It seems execve invalidates readOnlyMemFile_. Dunno why though.

[eteran]

Very interesting! Will have to look into this for sure.