PDA

View Full Version : Problem running binary


refyou
2008-03-01, 22:20
hi there,

I compiled XBMC on Ubuntu Desktop Edition 7.10 (Gutsy Gibbon) 32-bit for x86 following the : "HOW-TO compile XBMC for Linux from source code" instructions.

problem occurs while executing the newly compiled binary. After running it trough GDB here's the result:

user@laptop:~/XBMC$ gdb ./XboxMediaCenter
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) start
Breakpoint 1 at 0x85a560c: file XboxMediaCenter.cpp, line 39.
Starting program: /home/user/XBMC/XboxMediaCenter
[Thread debugging using libthread_db enabled]
[New Thread -1229150400 (LWP 10598)]
[Switching to Thread -1229150400 (LWP 10598)]
main (argc=1, argv=0xbf848814) at XboxMediaCenter.cpp:39
39 int main(int argc, char* argv[])
(gdb) continue
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) continue
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) continue
Continuing.

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb)

Any idea(s)?

BLKMGK
2008-03-02, 00:46
can you run it in debug mode and pastebin.com the XBMC.log file? The logfile gives pretty good info for the devs. You will also want to tell them what build this is as the code changes darn near hourly right now :-O

refyou
2008-03-02, 20:33
Thanks BLKMGK for your reaction. I am only using linux for a couple of weeks now, so not yet sure how to run debug or check versions etc. here's what I was able to retrieve.

Checked xbmc.log and saw :

18:36:58 T:3065927488 M:108277760 INFO: GLX Info: NOT Using destination window
18:36:58 T:3065927488 M:108277760 ERROR: GLX Error: No Multisample buffers available, FSAA disabled
18:36:58 T:3065927488 M:108277760 ERROR: GLX Error: No compatible framebuffers found

ran glxinfo and saw:

user@laptop:~$ glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method,
GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe,
GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig, GLX_MESA_copy_sub_buffer
client glx vendor string: ATI
client glx version string: 1.3
client glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
GLX_ARB_get_proc_address, GLX_SGI_video_sync, GLX_ARB_multisample,
GLX_ATI_pixel_format_float, GLX_ATI_render_texture
GLX version: 1.2
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
GLX_ARB_multisample
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.4 (2.1 Mesa 7.0.1)
OpenGL extensions:
GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_border_clamp,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3,
GL_ARB_transpose_matrix, GL_EXT_abgr, GL_EXT_blend_color,
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_texture_env_add,
GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
GL_EXT_texture_lod_bias

This laptop is a compaq m700 with an ati rage mobility card. It seems that it should support opengl but doesn't yet. It however will propably not support 2.0 :(

spiff
2008-03-02, 20:38
no dri - you dont have a proper driver for your card installed.

and rage mobility. isnt that like ANCIENT?

althekiller
2008-03-02, 21:04
http://www.google.com/search?hl=en&wikititle=1&q=Comparison%20of%20ATI%20Graphics%20Processing%20 Units#Rage_series

That doesn't list the mobility line but I'm sure it's based off one. Regardless, none of the rage series will cut the mustard.