• Login
  • Register
  • Dolphin Forums
  • Home
  • FAQ
  • Download
  • Wiki
  • Code


Dolphin, the GameCube and Wii emulator - Forums › Dolphin Emulator Discussion and Support › Support v
« Previous 1 ... 493 494 495 496 497 ... 1190 Next »

Crashes every time I try to run a game.
View New Posts | View Today's Posts

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
Crashes every time I try to run a game.
02-22-2015, 03:53 PM
#1
galundrux
Unregistered
 
Hi, hope someone here can help as I don't know what else to try.

I compiled the source from git today, 3 times now. Dependencies all seem to be fine. I'm useing the latest Nvidia drivers from Nvidia. Source compiles fine, and seems to run fine until I try to start a game. So far I've tested with Xenoblade and Super Mario Galaxy, they both crash Dolphin instantly. I've tried with default setting, and many more, includeing useing software render with the same results. Every time I get this output, which is not very helpful to me.

Code:
The program 'dolphin-emu' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
 (Details: serial 36 error_code 8 request_code 1 minor_code 0)
 (Note to programmers: normally, X errors are reported asynchronously;
  that is, you will receive the error a while after causing it.
  To debug your program, run it with the --sync command line
  option to change this behavior. You can then get a meaningful
  backtrace from your debugger if you break on the gdk_x_error() function.)
Aborted

Any help would be appreaciated.
Reply
02-22-2015, 04:03 PM (This post was last modified: 02-22-2015, 04:05 PM by Shonumi.)
#2
Shonumi Offline
Linux User/Tester
**********
Administrators
Posts: 6,503
Threads: 55
Joined: Dec 2011
Can you run Dolphin through gdb? If you can, run a backtrace (just type in "bt") to see what piece of code is causing the issue (or at least provide a clue).
Website Find
Reply
02-22-2015, 04:49 PM
#3
galundrux
Unregistered
 
I've never used gdb before, no matter how I try to launch dolphin with it it just says "No stack", maybe I'll read the man pages later. But if I run it with the --debugging option I get

Code:
(dolphin-emu:11781): GLib-GObject-WARNING **: invalid cast from `wxPizza' to `GtkNotebook'

(dolphin-emu:11781): Gtk-CRITICAL **: IA__gtk_notebook_get_n_pages: assertion `GTK_IS_NOTEBOOK (notebook)' failed

(dolphin-emu:11781): GLib-GObject-WARNING **: /tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gsignal.c:2459: signal `page-added' is invalid for instance `0x2b68e90'


I don't know if that's helpful? Dosen't look like it to me but what do I know.
Reply
02-22-2015, 06:58 PM (This post was last modified: 02-22-2015, 07:01 PM by Shonumi.)
#4
Shonumi Offline
Linux User/Tester
**********
Administrators
Posts: 6,503
Threads: 55
Joined: Dec 2011
Assuming you have Dolphin installed (not just compiled) just run

Code:
gdb dolphin-emu

Then type in "run" and hit Enter. Wait until Dolphin implodes, and see if it says anything useful. Of course, if you've already done these steps and you still get the "No stack" message, I'm stumped.

Ah, before I forget, you really should add the -g argument to g++ when compiling Dolphin. It's for debugging symbols. You can do this through Dolphin's CMakeList.txt file, adding a line like "ADD_DEFINITIONS(-g)" or something like that (google it since I'm bad at explaining).
Website Find
Reply
02-23-2015, 01:37 AM
#5
galundrux
Unregistered
 
Thanks, that helped, I was being stupid with the gdb command and didn't figure out I need to tell it to run. Here is what it spits out.

Code:
(gdb) run
Starting program: /usr/local/bin/dolphin-emu
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffc83a8700 (LWP 8727)]
[New Thread 0x7fffc7ba7700 (LWP 8728)]
[Thread 0x7fffc83a8700 (LWP 8727) exited]
[New Thread 0x7fffc83a8700 (LWP 8953)]
[Thread 0x7fffc7ba7700 (LWP 8728) exited]
[New Thread 0x7fffc7ba7700 (LWP 8979)]
[Thread 0x7fffc7ba7700 (LWP 8979) exited]
[New Thread 0x7fffc7ba7700 (LWP 9028)]
[Thread 0x7fffc83a8700 (LWP 8953) exited]
[New Thread 0x7fffc83a8700 (LWP 9042)]
[Thread 0x7fffc7ba7700 (LWP 9028) exited]
[New Thread 0x7fffc7ba7700 (LWP 9247)]
[New Thread 0x7fffc4ef7700 (LWP 9259)]
[New Thread 0x7fffb607d700 (LWP 9278)]
The program 'dolphin-emu' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 36 error_code 8 request_code 1 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Program received signal SIGSEGV, Segmentation fault.
0x0000000000bade4a in ?? ()
(gdb) bt
#0  0x0000000000bade4a in ?? ()
#1  0x00000000004bfcec in ?? ()
#2  0x000000000077ba94 in ?? ()
#3  0x000000000077bb36 in ?? ()
#4  0x000000000077bcfb in ?? ()
#5  0x000000000088883b in ?? ()
#6  0x0000000000abdc9e in ?? ()
#7  0x00007ffff5efbeeb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x00007ffff5efb355 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x00007ffff5efb688 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007ffff5efba82 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007ffff528b797 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#12 0x00000000009a5b45 in ?? ()
#13 0x00000000007804af in ?? ()
#14 0x000000000070c0c7 in ?? ()
#15 0x00000000007eb958 in ?? ()
#16 0x0000000000522798 in ?? ()
#17 0x00007ffff2ba5ead in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#18 0x0000000000443989 in _start ()
(gdb)

However I did semi-solve my problem by useing the gui just to configure it then running it useing "dolphin-emu-nogui -e game.iso", running it this way works fine and the games run great.
Reply
02-23-2015, 05:46 AM
#6
Shonumi Offline
Linux User/Tester
**********
Administrators
Posts: 6,503
Threads: 55
Joined: Dec 2011
Yeah, I guess it looks like gibberish (all of those ??) because there are no debugging symbols, sorry I forgot to tell you about them earlier :p

Anyway, it looks like it has something to do with GTK. Totally seems GUI related since you can run Dolphin using nogui version.
Website Find
Reply
« Next Oldest | Next Newest »


  • View a Printable Version
  • Subscribe to this thread
Forum Jump:


Users browsing this thread: 1 Guest(s)



Powered By MyBB | Theme by Fragma

Linear Mode
Threaded Mode