#How to find the cause of an exit crash that do not produce any error message nor backtrace?

16 messages · Page 1 of 1 (latest)

placid dagger
#

I need triplanar/box texture mapping. And thus I am trying to use bevy_triplanar_splatting, however the example in this repository just exits/crash before opening a window and do not produce any error/warning message nor a backtrace. Any idea on how I could find the cause of the exit/crash?

hallow whale
#

Run it though gdb

#

gdb target/debug/whatever.exe

#

Then hit r

placid dagger
#

So I had to modify the example code and the material code to load the assets and shader using an absolute path specific to me (but no worries, ok for debugging I suppose). However gdb did not help:

#

[New Thread 0x7ffff268d6c0 (LWP 134916)]
[New Thread 0x7ffff1d626c0 (LWP 134917)]
[New Thread 0x7ffff15616c0 (LWP 134918)]
[Thread 0x7ffff15616c0 (LWP 134918) exited]
[New Thread 0x7ffff15616c0 (LWP 134919)]
[New Thread 0x7ffff0be06c0 (LWP 134921)]
[New Thread 0x7fffe8bba6c0 (LWP 134936)]
[New Thread 0x7fffd8fff6c0 (LWP 134937)]
[Thread 0x7ffff0be06c0 (LWP 134921) exited]
[Thread 0x7ffff268d6c0 (LWP 134916) exited]
[Thread 0x7fffd8fff6c0 (LWP 134937) exited]
[Thread 0x7ffff15616c0 (LWP 134919) exited]
[Thread 0x7ffff1d626c0 (LWP 134917) exited]
[Thread 0x7ffff7f46980 (LWP 134881) exited]
[Thread 0x7fffe8bba6c0 (LWP 134936) exited]
[New process 134881]
[Inferior 1 (process 134881) exited normally]
(gdb) bt
No stack.
(gdb)

#

Also, trying to replicate this using only Bevy and no plugin, I tried all the shader examples. They all work correctly.

hallow whale
#

Did you compile in debug mode to ensure you got debug symbols?

placid dagger
#

yes, I did

hallow whale
#

I guess the next thing you can try is slowly start stripping out parts of your project until you find the thing responsible

hallow whale
placid dagger
#

I will try stripping some code from the example/plugin but this is not my project, it is a third party plugin I have no experience with. Trying to get some experience with it but it is a bit difficult giving the situation.

placid dagger
#

Thanks, after commenting pretty much all of the code (just leaving the insertion of the DefaultPlugins and the call to run(). I still had the issue. So I changed the Cargo.toml line default-features = false to true and this fixed the issue in question. I am not sure which feature is the cause. But this was a lot of work for an simple issue and simple workaround. Anyway, now I still have a empty window instead of the expected result, but this is an entirely different issue. Thanks

leaden lichen
#

you had default-features = false on bevy?

#

which features did you select manually?

#

i remember seeing an issue on the repo that was something like features a does not work if feature b is missing, so maybe you fell on one of this cases