eteran / edb-debugger

edb is a cross-platform AArch32/x86/x86-64 debugger.
GNU General Public License v2.0
2.68k stars 322 forks source link

Failed to read 0 bytes from "7eff8f10e100" #789

Closed zhqhzj closed 3 years ago

zhqhzj commented 3 years ago

please Report Bugs & Requests At: https://github.com/eteran/edb-debugger/issues comparing versions: [4864] [4864] Running Terminal: "/usr/bin/xterm" Terminal Args: ("-title", "edb output", "-hold", "-e", "sh", "-c", "tty > /tmp/edb_temp_file_2026599105_2648;trap \"\" INT QUIT TSTP;exec<&-; exec>&-;while :; do sleep 3600; done") Terminal process has TTY: "/dev/pts/2" Debuggee is now 32 bit Loading session file Loading plugin-data restoreComments Debuggee is now 64 bit Failed to read 0 bytes from "7eff8f10e100" Unable to get signal info for thread 2688 : PTRACE_GETSIGINFO failed: No such process Saving session file

ENV: VMware Workstation 12 player + ubuntu-20-04.1 + edb_1.3.0

eteran commented 3 years ago

Is this causing you any errors? That check is in there because sometimes some methods of reading don't work. So long as SOME methods work, this it shouldn't be a problem. Can you go into more detail?

zhqhzj commented 3 years ago

Hi,

------------------ 原始邮件 ------------------ 发件人: "eteran/edb-debugger" <notifications@github.com>; 发送时间: 2020年12月17日(星期四) 上午10:44 收件人: "eteran/edb-debugger"<edb-debugger@noreply.github.com>; 抄送: "Johnny.zhang"<416642205@qq.com>;"Author"<author@noreply.github.com>; 主题: Re: [eteran/edb-debugger] Failed to read 0 bytes from "7eff8f10e100" (#789)

Is this causing you any errors? That check is in there because sometimes some methods of reading don't work. So long as SOME methods work, this it shouldn't be a problem. Can you go into more detail?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

eteran commented 3 years ago

@zhqhzj If there was intended to be a message, it was not received. I only see "Hi"

eteran commented 3 years ago

I am closing this issue due to it not being clear what the issue is. Please reopen if you are able to provide more details.