Now, to get to the reason I signed up, I've compiled the latest SVN on ArchLinux and vbam itself works wonderful. On the other hand, gvbam, segfaults without giving any useful error. Is there anything I can do to help figure out why it does this?
Â
You can build a debug version by running "cmake -D CMAKE_BUILD_TYPE=Debug . && make"
And then generate a backtrace using gdb :
gdb ./gvbam
Type bt in the gdb console to get a backtrace.
Â
You think there has to be a rewrite in order to add some dialogs!?!
Not a full rewrite of course, but the config handling routines have to be rewritten to get a proper and maintainable code.
Now, to get to the reason I signed up, I've compiled the latest SVN on ArchLinux and vbam itself works wonderful. On the other hand, gvbam, segfaults without giving any useful error. Is there anything I can do to help figure out why it does this?
Â
You can build a debug version by running "cmake -D CMAKE_BUILD_TYPE=Debug . && make"
[elliott@eee-arch trunk]$ gdb ./gvbam
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
(gdb) bt
No stack.
(gdb)
Program received signal SIGSEGV, Segmentation fault.
[switching to Thread 0xb6bb0710 (LWP 25697)]
0xb710d596 in glViewport () from /usr/lib/libGL.so.1
(gdb) bt
#0 0xb710d596 in glViewport () from /usr/lib/libGL.so.1
#1 0x0808612b in VBA::ScreenAreaGl::vOnWidgetResize (this=0xa05d0c0) at /home/elliott/temp/trunk/src/gtk/screenarea-opengl.cpp:81
#2 0x08083477 in VBA::ScreenArea::vUpdateSize (this=0xa05d0c0) at /home/elliott/temp/trunk/src/gtk/screenarea.cpp:221
#3 0x080865f9 in ScreenAreaGl (this=0xa05d0c0, _iWidth=240, _iHeight=160, _iScale=1) at /home/elliott/temp/trunk/src/gtk/screenarea-opengl.cpp:44
#4 0x08089ed9 in VBA::Window::vApplyConfigScreenArea (this=0x9c3ad60) at /home/elliott/temp/trunk/src/gtk/window.cpp:620
#5 0x0808e8da in Window (this=0x9c3ad60, _pstWindow=0x9bfa8f8, _poXml=@0xbf980afc) at /home/elliott/temp/trunk/src/gtk/window.cpp:144
#6 0x0807285d in main (argc=1, argv=0xbf980c04) at /usr/include/libglademm-2.4/libglademm/xml.h:307
[/code]
Thanks for the backtrace. I've been able to reproduce the crash on my system (by using a recent MESA GL driver instead of the one provided by nVidia). However I've not been able to fix it yet.
Â
A workaround until the bug is fixed is to use a different output module in VBA-M.
To use the Xv output module, modify the config file (~/.config/gvbam/config), to something like :
Thanks a lot for your answer [img]<fileStore.core_Emoticons>/emoticons/smile.png[/img]/emoticons/smile@2x.png 2x" width="20" height="20" /> :banana_confusion:
Â
EDIT:
Â
already I compiled and installed the emulator, apparently it does not have cheat support...
Â
can I do a request about it?
Last edited by zuargo on Sun Nov 01, 2009 8:46 pm, edited 1 time in total.
i'm absolutley new to any of this stuff, so could anybody explain step by step how to do this? I know it sounds like a retarded question but haven't got a about any of this. also, are you talking about gba link, or is that different?