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

Jump to my own already opened source file first on crash in debugger #8090

Closed
xgdgsc opened this issue Sep 2, 2021 · 1 comment
Closed

Comments

@xgdgsc
Copy link

xgdgsc commented Sep 2, 2021

Type: Feature Request

Now when I debug the program crashes and it opens some file I' ve never touched like /usr/src/debug/glibc-2.17-c758a686/nptl/sysdeps/unix/sysv/linux/raise.c first. I have to open the left long call stack to scroll and select my own file to see which line I wrote might have problem (which usually is already opened inside the window before launch of program).

Since clicking on the call stack finally could open my own source file. I guess it' s possible to make the extension work for me to iterate the crashed call stack and find the most relevent file in priority like: Currently Opened/Viewd File > Files in user Home folder > Files in system path. And show me the file with highest likelihood of the bug for me, which I believe would save a lot of time navigating through stack files.

@WardenGnaw
Copy link
Member

raise.c is the source where exceptions are actually thrown.

This is the "Just my Code" feature.

Duplicate of: #5763

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

No branches or pull requests

2 participants