Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ql.run(begin=begin)时,qdb的cur_addr不在begin #1

Open
msxfXF opened this issue Oct 25, 2022 · 1 comment
Open

ql.run(begin=begin)时,qdb的cur_addr不在begin #1

msxfXF opened this issue Oct 25, 2022 · 1 comment

Comments

@msxfXF
Copy link

msxfXF commented Oct 25, 2022

在某些场景下,只想调试指定范围的代码。
启用debuger后,ql.run(begin=begin)时,qdb的PC不在begin位置;而与此同时,gdb却可以正常跳到begin位置运行。

怀疑是qdb.py中,76行到82行之间,对self.ql.loader.entry_point的赋值逻辑有问题,可能没顾及到run中传入的begin即self.ql.entry_point的值。

if self.ql.os.type == QL_OS.BLOB:
            self.ql.loader.entry_point = self.ql.loader.load_address

        elif init_hook and self.ql.loader.entry_point != init_hook:
            self.do_breakpoint(init_hook)

        self.cur_addr = self.ql.loader.entry_point
@ucgJhe
Copy link
Owner

ucgJhe commented Nov 4, 2022

@msxfXF 你好 感謝你的反饋,請問有可以重現的範例嗎?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants