Re: MesaLib

[Robert Swindells <rjs%fdy2.co.uk@localhost>]

Taylor R Campbell <campbell+netbsd-tech-x11%mumble.net@localhost> wrote:
> Date: Sun, 09 Jul 2023 22:42:43 +0100
> From: Robert Swindells <rjs%fdy2.co.uk@localhost>
>> 
>> Reading symbols from /usr/X11R7/bin/glxgears...
>> [New process 1375]
>> [New process 1357]
>> Core was generated by `glxgears'.
>> Program terminated with signal SIGSEGV, Segmentation fault.
>> #0  0x00007f7ff0969435 in ?? ()
>> [Current thread is 1 (process 1375)]
>> (gdb) bt
>> #0  0x00007f7ff0969435 in ?? ()
>> #1  0x00007f7fffffdfa0 in ?? ()
>> #2  0x00007f7ff74ce6c0 in ?? ()
>> #3  0x00007f7ff242881f in ?? ()
>> #4  0x0000000000000000 in ?? ()
>
> Do you have the debug set installed?

I thought I did but had not built them.

> Do you have these files?
>
> /usr/libdata/debug/usr/X11R7/bin/glxgears.debug
> /usr/libdata/debug/usr/X11R7/lib/libGL.so.*.0.debug
> /usr/libdata/debug/usr/X11R7/lib/libglapi.so.*.0.debug
> /usr/libdata/debug/usr/X11R7/lib/modules/dri/*_dri.so.*.debug

They were out of date.

> If you run glxgears under gdb and set a breakpoint on main before
> starting it, does it appear to have better debug data?

It dies somwhere after nv30_push_vbo().

Using the new tree on the old AMD card does run glxgears fine so I
think this is just a bug in the gallium nouveau code.