amethyst / amethyst/rustrogueliketutorial
Core dump when running Chapter 1
- Linguagem predominante
- Rust
- Estrelas
- 970
- Forks
- 166
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
Hi, I'm new to Rust and gamedev, and unfortunately I've stuck at the very first chapter. Both an independent project following the tutorial and the cloned repo yield the same error when I run them after building. Other rust programs and rust projects I've written build and run fine; I am not sure if it is caused by an issue with the bterm builder creating a window that my system does not like. I would greatly appreciate the help!
```
Finished dev [optimized + debuginfo] target(s) in 0.10s
Running `[MY_DIRECTORY}/rustrogueliketutorial/target/debug/chapter-01-hellorust`
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
chapter-01-hellorust: xcb_io.c:269: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted (core dumped)
```
Journalctl yields the core dump as:
```
Process 24894 (chapter-01-hell) of user 1000 dumped core.
Stack trace of thread 24894:
#0 0x00007f32fdba8d22 raise (libc.so.6 + 0x3cd22)
#1 0x00007f32fdb92862 abort (libc.so.6 + 0x26862)
#2 0x00007f32fdb92747 __assert_fail_base.cold (libc.so.6 + 0x26747)
#3 0x00007f32fdba1616 __assert_fail (libc.so.6 + 0x35616)
#4 0x00007f32fda3ad2d n/a (libX11.so.6 + 0x40d2d)
#5 0x00007f32fda3adc8 n/a (libX11.so.6 + 0x40dc8)
#6 0x00007f32fda3b182 _XEventsQueued (libX11.so.6 + 0x41182)
#7 0x00007f32fda3e176 _XGetRequest (libX11.so.6 + 0x44176)
#8 0x00007f32fda29395 XNoOp (libX11.so.6 + 0x2f395)
#9 0x00007f32fd3376e3 n/a (libGLX_mesa.so.0 + 0x306e3)
#10 0x00007f32fd4cb428 n/a (libGLX.so.0 + 0x1b428)
#11 0x000055a6cbdbefa5 n/a (/[MY_DIRECTORY]/rustrogueliketutorial/target/debug/chapter-01-hel>
```
My system is Manjaro Linux , x86_64 with i3 as the windows manager.
Guia de contribuição
Nenhum guia de contribuição indexado para este repositório
Avaliação
Esta issue ainda não foi avaliada.