ChanServ changed the topic of #panfrost to: Panfrost - FLOSS Mali Midgard + Bifrost + Valhall - Logs https://oftc.irclog.whitequark.org/panfrost
rasterman has quit [Quit: Gettin' stinky!]
sally has quit []
sally has joined #panfrost
alarumbe has quit [Remote host closed the connection]
sally has quit [Quit: ZNC 1.10.1 - https://znc.in]
sally has joined #panfrost
warpme has joined #panfrost
digetx has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
digetx has joined #panfrost
pjakobsson has joined #panfrost
rasterman has joined #panfrost
warpme has quit []
warpme has joined #panfrost
alarumbe has joined #panfrost
warpme has quit []
warpme has joined #panfrost
warpme has quit []
dsimic is now known as Guest23742
dsimic has joined #panfrost
Guest23742 has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]
<olivial> junari: so what I had in mind was run the program under gdb like 'gdb ppsspp'. It should give you a prompt, where you can set a breakpoint with 'break __vk_errorv'. It will probably give you a prompt where it asks if you want to create it even though the symbol is unknown. Say yes to that. Then do 'run', and it should start the program and then stop at the breakpoint when the error occurs. Then you can run 'bt' to get a backtrace that tells you
<olivial> were the error came from
<HdkR> potentially with a `handle SIGSEGV SIGBUS nostop`
<HdkR> But I assume it'll be early enough that it won't hit the magic :)
<olivial> oh, just realized they aren't in the channel anymore
<olivial> there's also <https://gitlab.freedesktop.org/mesa/mesa/-/issues/13679>, which appears to be the same problem (possibly reported by junari?)
soreau has quit [Ping timeout: 480 seconds]
soreau has joined #panfrost