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

failed to update thread frames during python debugging #7264

Closed
tom-shan opened this issue Mar 3, 2020 · 10 comments
Closed

failed to update thread frames during python debugging #7264

tom-shan opened this issue Mar 3, 2020 · 10 comments
Labels
bug bugs found in the application critical critical bugs / problems debug issues that related to debug functionality vscode issues related to VSCode compatibility

Comments

@tom-shan
Copy link
Contributor

tom-shan commented Mar 3, 2020

Description

When debugging python file, Call Stack will show the message of Load More Stack Frames.
it will show thread frames only after clicking this message.
image

Reproduction Steps

1 download vscode python plugin
2 start theia
3 create a simple python file and add a breakpoint
4 debug this python file and click Step Over

OS and Theia version:
OS: centos 7
Theia: 6d0abe5
Diagnostics:
a regression caused by d1678ad

@tom-shan
Copy link
Contributor Author

tom-shan commented Mar 3, 2020

I think we should put d1678ad#diff-bb75a296f1f7fdc09c2d755ef791d61cR229 in the branch of if (thread.stoppedDetails && thread.stoppedDetails.allThreadsStopped) accoring to it's commit message.

@akosyakov akosyakov added bug bugs found in the application debug issues that related to debug functionality labels Mar 3, 2020
@akosyakov
Copy link
Member

akosyakov commented Mar 3, 2020

@marcdumais-work @marechal-p Could you have a look please? It seems to be caused by the recently merged PR or revert it I would prefer to step back and make a minimal change which does not break it.

@akosyakov akosyakov added vscode issues related to VSCode compatibility critical critical bugs / problems labels Mar 3, 2020
@marcdumais-work
Copy link
Contributor

Reproduced on master. Will now confirm if same happens or not before d1678ad

@marcdumais-work
Copy link
Contributor

Will now confirm if same happens or not before d1678ad

Confirmed - testing one commit before d1678ad, the call stack frames are displayed after stepping, without having to click on "load more stack frames".

I will talk with @marechal-p before reverting, but this looks like we will likely proceed doing this later today.

@akosyakov
Copy link
Member

akosyakov commented Mar 4, 2020

@marcdumais-work Can we have a PR to revert d1678ad please? It breaks products which use next version. A proper PR can be reintroduced later. Let me know if you don't have time I will revert it. btw was it a part of last release? We need a bug fix release probably then as well.

@marcdumais-work
Copy link
Contributor

Can we have a PR to revert d1678ad please?

Yes, we'll either have a fix or revert that commit today.

@marcdumais-work
Copy link
Contributor

btw was it a part of last release?

Indeed it was.

We need a bug fix release probably then as well.

+1

@paul-marechal
Copy link
Member

paul-marechal commented Mar 4, 2020

From my investigation, it seems that for some reason, the DebugStackFramesSource.getElements function is not called on stop, when replicating the situation mentioned by this issue.

*getElements(): IterableIterator<TreeElement> {

I wasn't able to make sense of what doesn't happen/what would need to happen to fix that, and I need to focus on other tasks for now.

@marcdumais-work
Copy link
Contributor

I wasn't able to make sense of what doesn't happen/what would need to happen to fix that, and I need to focus on other tasks for now.

Thanks for the investigation @marechal-p - We'll revert the PR for now and do a bugfix release.

@marcdumais-work
Copy link
Contributor

The original PR is reverted - we'll make sure this issue here is no longer present if we bring it back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug bugs found in the application critical critical bugs / problems debug issues that related to debug functionality vscode issues related to VSCode compatibility
Projects
None yet
Development

No branches or pull requests

4 participants