Skip to content

pycdb behaves badly if you breakpoint on a module without symbols #10

@ASKobayashi

Description

@ASKobayashi

I set a breakpoint using symbolic notation (something like "jscript9!Js::Math::Atan2") and ran pycdb. It went into a neverending loop spinning without notification.

Debugging by printing the read thread input yielded:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\System32\jscript9.dll - C:\Windows\System32\jscript9.dll
Breakpoint 0's offset expression evaluation failed.
Check for invalid symbols or bad syntax.

We should probably do something to prevent the silent death-spin..

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions