[Libva] segmentation fault with vainfo

[Gwenole Beauchesne]

Hi,

On Thu, 14 Apr 2011, Achim Hofmann wrote:

> [0x86af1d4] avcodec decoder: Using VA API version 0.32 for hardware
> decoding.
> libva: libva version 0.32.0-sds2
> Xlib:  extension "XFree86-DRI" missing on display ":0".
> libva: va_getDriverName() returns 0
> libva: Trying to open /usr/lib/va/drivers/fglrx_drv_video.so
> libva: va_openDriver() returns 0
> xvba_video: XVBA_GetSurface(): status 2
>
> I'm not really sure whether I should have a good feeling with the last
> line or not.

This can happen, depending on the Catalyst driver version or the type of 
contents (interlaced?). Anything >= 10.12 should be fine unless a 
regression happened.

> Okay, let's have a look at the output of vainfo:
>
> libva: libva version 0.32.0-sds2
> Xlib:  extension "XFree86-DRI" missing on display ":0.0".
> libva: va_getDriverName() returns 0
> Segmentation fault

Please make sure you use the right vainfo program, and not something from 
a custom built libva:
$ which vainfo
$ ldd $(which vainfo)

There is a bug in va.c whereby a NULL driver_name would cause the function 
to crash, thus the application too. That's a sure thing that can be fixed, 
someone sent me a patch. However, there is another problem, possibly 
related to the driver detection code but I never could reproduce it.

Besides, make sure *all* your VA-API applications (vainfo, vlc, mplayer, 
etc.) or libraries (ffmpeg) are built from the very same libva. The 
xvba-video 0.7.8 binaries I provide are built from our libva but it works 
fine with any libva == 1.0.1, [ 1.0.3 - 1.0.10 ].

> However, mplayer from splitted-desktop.com works like a charm without
> any errors.

The pre-built binary or something you rebuilt yourself?

> Do you have any idea what could be the reason for the segmentation fault
> of vainfo? If I have to add more information, please let me know.

Please build libva with debug symbols and:
$ gdb vainfo
(`run')
(`bt' when it crashes)

Regards,
Gwenole.