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

debug: Rust backtraces in alvr_client_core show <unknown> unwind frames #1583

Closed
4 of 5 tasks
ShootingKing-AM opened this issue Apr 13, 2023 · 4 comments · Fixed by alvr-org/PhoneVR#188
Closed
4 of 5 tasks
Labels

Comments

@ShootingKing-AM
Copy link
Member

ShootingKing-AM commented Apr 13, 2023

Description

Rust backtraces in alvr_client_core show unwind frames. Eg.

05:04:24.799  8514-8601  [ALVR NATIVE-RUST] pid-8514 E  What happened:
 panicked at 'called `Result::unwrap()` on an `Err` value: ErrorResult(ErrorUnknown)', alvr\client_core\src\platform\android.rs:465:18
 Backtrace:
	0: <unknown>
	1: <unknown>
	2: <unknown>
	3: <unknown>
	4: <unknown>
	5: <unknown>
	6: <unknown>
	7: <unknown>
	8: <unknown>
	9: <unknown>
	10: <unknown>
	11: <unknown>
	12: <unknown>

On latest master. With and without xtask --release flag.

General Troubleshooting

  • I carefully followed the instructions in the README and successfully completed the setup wizard
  • I read the ALVR Wikis here and here

Environment

Hardware

Tested on android api levels 27, 30, 32. Both with a real android device (Android level 12) and AVDs

Installation

ALVR Version: Master (20v-dev10)

Install Type:

  • Packaged (exe, deb, rpm, etc)
  • Portable (zip)
  • Source

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions):

  • Windows - Visual Code + gitbash - alvr-carboard/prepare-deps.sh + cargo xtask build-client-lib [--release]
    image
@ShootingKing-AM
Copy link
Member Author

@stale
Copy link

stale bot commented May 18, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label May 18, 2023
@ShootingKing-AM
Copy link
Member Author

ShootingKing-AM commented May 19, 2023

#1610

@stale stale bot removed the stale label May 19, 2023
@stale
Copy link

stale bot commented Jun 22, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

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

Successfully merging a pull request may close this issue.

1 participant