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

AMD CodeXL always detects a segfault when running Rust code on Windows #26590

Closed
tomaka opened this issue Jun 26, 2015 · 6 comments
Closed

AMD CodeXL always detects a segfault when running Rust code on Windows #26590

tomaka opened this issue Jun 26, 2015 · 6 comments

Comments

@tomaka
Copy link
Contributor

@tomaka tomaka commented Jun 26, 2015

I had already reported this problem in #15644 but it was ignored. I'm reopening an issue for this.

When running any Rust program inside AMD CodeXL, a second-chance exception is immediatly detected (see screenshot). As I said in #15644 it used to work at some point in the past.

This happens even with an empty Rust program (with an empty main).

To be sure, I tried running CodeXL with a C program compiled with MinGW, and it works perfectly fine.

@tomaka tomaka changed the title AMD CodeXL always detects an exception when running Rust code on Windows AMD CodeXL always detects a segfault when running Rust code on Windows Jun 26, 2015
@nagisa
Copy link
Member

@nagisa nagisa commented Jun 29, 2015

Is there any way to see backtrace at the time of exception?

@tomaka
Copy link
Contributor Author

@tomaka tomaka commented Jun 29, 2015

I don't think so :-/

@tomaka
Copy link
Contributor Author

@tomaka tomaka commented Aug 5, 2015

This doesn't happen with programs compiled with the MSVC nightly.

@brson
Copy link
Contributor

@brson brson commented Jan 26, 2017

Still a bug?

@tomaka
Copy link
Contributor Author

@tomaka tomaka commented Jan 26, 2017

AMD CodeXL only runs if you have an AMD GPU, and unfortunately I have changed my hardware about a year ago. Therefore I can't check anymore.

@steveklabnik
Copy link
Member

@steveklabnik steveklabnik commented Jan 26, 2017

Then, let's give this a close.

If anyone has this issue and can reproduce, please let me know, and we'll reopen. Thanks!

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

Successfully merging a pull request may close this issue.

None yet
4 participants