ChanServ changed the topic of #zink to: official development channel for the mesa3d zink driver || https://docs.mesa3d.org/drivers/zink.html
konstantin_ has joined #zink
konstantin is now known as Guest603
konstantin_ is now known as konstantin
Guest603 has quit [Ping timeout: 480 seconds]
<fdobridge> <z​mike.> if any python enthusiasts are around, https://gitlab.freedesktop.org/mesa/mesa/-/issues/10513 needs fixing pretty urgently considering the volume of tickets piling up around it
omegatron has quit [Quit: What happened? You quit!]
<fdobridge> <t​heevilskeleton> @zmike. I'm familiar with Python, but I know nothing about mesa :/
<fdobridge> <t​heevilskeleton> I could help tomorrow with proper guidance
<fdobridge> <o​rowith2os> "Even worse, it's annoying to handle because the (current) XML doesn't have promotedto tags for all promoted extensions, so there's no way to link an EXT to a KHR." this might actually be amazing for Wayland
<fdobridge> <o​rowith2os> though it'll probably only be *useful* if it can automatically redirect from "promotedto-tagged" protocols to the ones being promotedto
<fdobridge> <o​rowith2os> just a random thought
sumoon has quit [Remote host closed the connection]
dubiousness has quit [Remote host closed the connection]
sumoon has joined #zink
dubiousness has joined #zink
<fdobridge> <t​heevilskeleton> MERGEEEEDDDD
DodoGTA has quit [Remote host closed the connection]
DodoGTA has joined #zink
DodoGTA has quit [Quit: DodoGTA]
DodoGTA has joined #zink
DodoGTA has quit [Quit: DodoGTA]
DodoGTA has joined #zink
<fdobridge> <o​rowith2os> @zmike. can you show me the results of the `gdb attach` method you mentioned?
<fdobridge> <o​rowith2os> on another note, would a debug flag for Zink be useful
<fdobridge> <z​mike.> I don't know what you're asking
<fdobridge> <o​rowith2os> I don't have any clue on what to expect with "gdb attach and break on some zink function"ing
<fdobridge> <o​rowith2os> `ZINK_THE_ALL_KNOWING_GL_DRIVER=1`
<fdobridge> <z​mike.> `gdb --pid <pid of your process>` -> `break zink_update_barriers` -> if it stops you are using zink
<fdobridge> <o​rowith2os> ah
<fdobridge> <o​rowith2os> damn
<fdobridge> <o​rowith2os> attaching just locks up the processes
<fdobridge> <o​rowith2os> without even going to break
<fdobridge> <z​mike.> that's expected
<fdobridge> <z​mike.> ah, you also need `continue` after the break command
<fdobridge> <o​rowith2os> no, I mean, I `gdb --pid number` and it immediately locks up
<fdobridge> <z​mike.> yes, that's how it works
<fdobridge> <o​rowith2os> oh
<fdobridge> <o​rowith2os> I continue *after* attaching
<fdobridge> <o​rowith2os> and then I can break
Dark-Show has joined #zink
pbsds has quit [Ping timeout: 480 seconds]
jhli has quit []
<fdobridge> <g​fxstrand> @zmike. Future you needs to teach future me about this whole time machine back-porting trick. Seems like it'd save a lot of effort in the here and now.