Open 0323pin opened 3 months ago
So, I've clone the repo locally, applied the above patches and built rio
with the debug symbols on.
Here's the resulting backtrace:
~> set-env RUST_BACKTRACE "full"
~> rio
thread 'main' panicked at /home/pin/Git/rio/sugarloaf/src/context/mod.rs:100:14:
Request adapter
stack backtrace:
0: 0x26977c0 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h64b379b49e1ac14c
1: 0x26c62d3 - core::fmt::write::hffad184a3e8a29fd
2: 0x267ff99 - std::io::Write::write_fmt::h898ad85f5400c6c1
3: 0x26975a8 - std::sys_common::backtrace::print::hfd142b535fa244a2
4: 0x2698229 - std::panicking::default_hook::{{closure}}::h0b2841cddcb5179d
5: 0x2697ef2 - std::panicking::default_hook::hb55ff70a667c0912
6: 0x2698781 - std::panicking::rust_panic_with_hook::hf0fd20f889dcc3a2
7: 0x2698626 - std::panicking::begin_panic_handler::{{closure}}::hf70ee2d56df2cd9e
8: 0x26979d9 - std::sys_common::backtrace::__rust_end_short_backtrace::h2bcae7246dcb03a5
9: 0x2698377 - rust_begin_unwind
10: 0x73c6a3 - core::panicking::panic_fmt::h54accd437c2365a4
11: 0x26c855c - core::panicking::panic_display::h3f559986d8c35394
12: 0x73c0ec - core::option::expect_failed::hfe05ab716a1704a1
13: 0x1d7428c - core::option::Option<T>::expect::hf459028b2b901c2b
at /usr/pkgsrc/wip/rust179/work/rustc-1.79.0-src/library/core/src/option.rs:895:21
14: 0x8a01a2 - sugarloaf::context::Context::new::{{closure}}::hdc78f2e28a5ed39b
at /home/pin/Git/rio/sugarloaf/src/context/mod.rs:93:23
15: 0x7e1220 - sugarloaf::sugarloaf::Sugarloaf::new::{{closure}}::h1549472fcadf491d
at /home/pin/Git/rio/sugarloaf/src/sugarloaf.rs:120:50
16: 0x7c470b - rio::screen::Screen::new::{{closure}}::h36417bcfd846877a
at /home/pin/Git/rio/frontends/rioterm/src/screen/mod.rs:159:10
17: 0x88553a - rio::router::RouteWindow::new::{{closure}}::hf5609a978315b9b0
at /home/pin/Git/rio/frontends/rioterm/src/router/mod.rs:365:82
18: 0x80907c - rio::sequencer::Sequencer::run::{{closure}}::hdfceb00f487f15c6
at /home/pin/Git/rio/frontends/rioterm/src/sequencer.rs:63:18
19: 0x8587ea - rio::main::{{closure}}::h1f3516d14b586e2d
at /home/pin/Git/rio/frontends/rioterm/src/main.rs:149:50
20: 0x794e13 - tokio::runtime::park::CachedParkThread::block_on::{{closure}}::h577a4f16ba7f1265
at /home/pin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.37.0/src/runtime/park.rs:281:63
21: 0x794c6e - tokio::runtime::coop::with_budget::h88ae03db5d966fac
at /home/pin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.37.0/src/runtime/coop.rs:107:5
22: 0x794c6e - tokio::runtime::coop::budget::h0618cc0523b111fa
at /home/pin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.37.0/src/runtime/coop.rs:73:5
23: 0x794c6e - tokio::runtime::park::CachedParkThread::block_on::h917c79e45e27046e
at /home/pin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.37.0/src/runtime/park.rs:281:31
24: 0x812772 - tokio::runtime::context::blocking::BlockingRegionGuard::block_on::hbd4155abba16ce0a
at /home/pin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.37.0/src/runtime/context/blocking.rs:66:9
25: 0x780c79 - tokio::runtime::scheduler::multi_thread::MultiThread::block_on::{{closure}}::h32d608fba8768f78
at /home/pin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.37.0/src/runtime/scheduler/multi_thread/mod.rs:87:13
26: 0x7f8dc5 - tokio::runtime::context::runtime::enter_runtime::h2a0d130d5b69c2c1
at /home/pin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.37.0/src/runtime/context/runtime.rs:65:16
27: 0x780bfa - tokio::runtime::scheduler::multi_thread::MultiThread::block_on::h63782f3a604144f3
at /home/pin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.37.0/src/runtime/scheduler/multi_thread/mod.rs:86:9
28: 0x806196 - tokio::runtime::runtime::Runtime::block_on::h2aaf9818535970a6
at /home/pin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.37.0/src/runtime/runtime.rs:351:45
29: 0x8d0fda - rio::main::h660e553ea9dbe216
at /home/pin/Git/rio/frontends/rioterm/src/main.rs:155:5
30: 0x748b4b - core::ops::function::FnOnce::call_once::h281b9df121ef66e9
at /usr/pkgsrc/wip/rust179/work/rustc-1.79.0-src/library/core/src/ops/function.rs:250:5
31: 0x804a4e - std::sys_common::backtrace::__rust_begin_short_backtrace::h2e97682ccb8e71b7
at /usr/pkgsrc/wip/rust179/work/rustc-1.79.0-src/library/std/src/sys_common/backtrace.rs:155:18
32: 0x782561 - std::rt::lang_start::{{closure}}::hee1cb4c2a5c3093a
at /usr/pkgsrc/wip/rust179/work/rustc-1.79.0-src/library/std/src/rt.rs:159:18
33: 0x2698267 - std::panicking::try::h89c5172be281790d
34: 0x26a5938 - std::rt::lang_start_internal::h7cd5c2ba0d56d034
35: 0x78253a - std::rt::lang_start::hb45a14bffd4e3e5a
at /usr/pkgsrc/wip/rust179/work/rustc-1.79.0-src/library/std/src/rt.rs:158:17
36: 0x8d10ae - main
37: 0x739375 - ___start
at /usr/src/lib/csu/common/crt0-common.c:349:2
Any ideas?
Thanks for the issue!
Hmmm, would be nice to patch those changes on Rio/"winit fork" as well. Regarding the second error you sent, looks the "Request adapter" couldn't be created, this happens when wgpu cannot create an adapter using vulkan/gl/...
I can make a PR if you would like but, ...
would be nice to patch those changes on Rio/"winit fork" as well.
Where do I find that fork? I didn't see it on the branches you have here at github.
looks the "Request adapter" couldn't be created, this happens when wgpu cannot create an adapter using vulkan/gl/...
NetBSD doesn't have vulkan but, I've tried setting the wgpu environment variable to gl and that didn't help.
@0323pin
Where do I find that fork? I didn't see it on the branches you have here at github.
It's a directory in the repository. See here.
Cheers @TornaxO7 ... I should have looked.
Also, this made me think about something else.
looks the "Request adapter" couldn't be created, this happens when wgpu cannot create an adapter using vulkan/gl/...
@raphamorim Would you spare me some grep
and point me to where exactly the request is being made? Could be a ${PATH}
issue. Worth discarding that otherwise.
@0323pin did you try using the renderer property? https://raphamorim.io/rio/docs/config/renderer
Something like this:
[renderer]
performance = "High"
backend = "GL"
I am curious though because if vulkan leads to error then Rio uses OpenGl as fallback.
Last time I've tried
rio
on NetBSD, it was at version 0.0.34At the time, I faced this issue, https://github.com/raphamorim/rio/issues/376
Now, that there's v0.1.1, I thought I would try again.
The following three patches are required for it to build on NetBSD:
Unfortunately, it still won't run :(
Setting RUST_BACKTRACE=full doesn't tell me more,
Neither does
gdb
Of course, as release is built without debugging symbols. But, I need the patches to build the package, so building with
cargo
only isn't as simple.ktruss
is probably a little more helpful.Any thoughts? Thanks!