09-13-2014, 12:44 PM
On the line of the tests I did, I find a crash on FMV of FFXII for both 1.2.2 and latest git.
On GSdx, going to software works, but if I use hardware mode I get an assertion fail on any FMV:
/****************************************************************************************************************/
/home/antoine/Source/pcsx2-git/common/src/Utilities/Linux/LnxHostSys.cpp(64) : assertion failed:
Function: void SysPageFaultSignalFilter(int, siginfo_t*, void*)
Thread: MTGS
Condition: false
Message: Unhandled page fault @ 0x00000000
Stacktrace:
[00] __kernel_rt_sigreturn
[01] 0x0xf18ee0e0
[02] 0x0xf18bc067
[03] 0x0xf18bd573
[04] 0x0xf18d5712
[05] 0x0xf18dc137
[06] 0x0xf18e67fa
[07] GSgifTransfer
/****************************************************************************************************************/
Nothing interesting on the terminal and gdb(at least for me)
It crashes both on my desktop(nvidia gt770) and laptop(intel hd4000). Don't know for windows as I don't possess it.
For zzogl, the crash message is on the terminal :
The program 'pcsx2' received an X Window System error.
This probably reflects a bug in the program.
The error was The program 'pcsx2' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadFBConfig'.
(Details: serial 31 error_code 178 request_code 155 minor_code 34)
(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.)
Erreur de segmentation (core dumped)'GLXBadFBConfig'.
(Details: serial 31 error_code 178 request_code 155 minor_code 34)
(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.)
Erreur de segmentation (core dumped)
The backtrace being:
#0 0x0822020c in GSFrame:
nUpdateTitle(wxTimerEvent&) ()
#1 0x081dcb20 in Pcsx2App::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) ()
#2 0x081dcadd in Pcsx2App::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) const ()
#3 0xf7f20808 in wxEvtHandler:
rocessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) () from /usr/lib32/libwx_baseu-2.8.so.0
#4 0xf7f20be4 in wxEvtHandler:
earchDynamicEventTable(wxEvent&) () from /usr/lib32/libwx_baseu-2.8.so.0
#5 0xf7f20cbe in wxEvtHandler:
rocessEvent(wxEvent&) () from /usr/lib32/libwx_baseu-2.8.so.0
#6 0xf7ceed12 in wxTimerBase::Notify() () from /usr/lib32/libwx_gtk2u_core-2.8.so.0
#7 0xf7be912a in ?? () from /usr/lib32/libwx_gtk2u_core-2.8.so.0
#8 0xf6e14bb1 in ?? () from /usr/lib32/libglib-2.0.so.0
#9 0xf6e14097 in g_main_context_dispatch () from /usr/lib32/libglib-2.0.so.0
#10 0xf6e14458 in ?? () from /usr/lib32/libglib-2.0.so.0
#11 0xf6e14753 in g_main_loop_run () from /usr/lib32/libglib-2.0.so.0
#12 0xf73cba75 in gtk_main () from /usr/lib32/libgtk-x11-2.0.so.0
#13 0xf7bde9d3 in wxEventLoop::Run() () from /usr/lib32/libwx_gtk2u_core-2.8.so.0
#14 0xf7c6f584 in wxAppBase::MainLoop() () from /usr/lib32/libwx_gtk2u_core-2.8.so.0
#15 0xf7c6f0e0 in wxAppBase:
nRun() () from /usr/lib32/libwx_gtk2u_core-2.8.so.0
#16 0xf7ebe706 in wxEntry(int&, wchar_t**) () from /usr/lib32/libwx_baseu-2.8.so.0
#17 0xf7ebe7a3 in wxEntry(int&, char**) () from /usr/lib32/libwx_baseu-2.8.so.0
#18 0x081db87b in main ()
Hope it helps, but, I try to use the debugger to see what causes the bug on gsdx but it fails miserably before I get read anything meaningful. I guess it's related to something in the problem right... But not fully sure either.
On GSdx, going to software works, but if I use hardware mode I get an assertion fail on any FMV:
/****************************************************************************************************************/
/home/antoine/Source/pcsx2-git/common/src/Utilities/Linux/LnxHostSys.cpp(64) : assertion failed:
Function: void SysPageFaultSignalFilter(int, siginfo_t*, void*)
Thread: MTGS
Condition: false
Message: Unhandled page fault @ 0x00000000
Stacktrace:
[00] __kernel_rt_sigreturn
[01] 0x0xf18ee0e0
[02] 0x0xf18bc067
[03] 0x0xf18bd573
[04] 0x0xf18d5712
[05] 0x0xf18dc137
[06] 0x0xf18e67fa
[07] GSgifTransfer
/****************************************************************************************************************/
Nothing interesting on the terminal and gdb(at least for me)
It crashes both on my desktop(nvidia gt770) and laptop(intel hd4000). Don't know for windows as I don't possess it.
For zzogl, the crash message is on the terminal :
The program 'pcsx2' received an X Window System error.
This probably reflects a bug in the program.
The error was The program 'pcsx2' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadFBConfig'.
(Details: serial 31 error_code 178 request_code 155 minor_code 34)
(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.)
Erreur de segmentation (core dumped)'GLXBadFBConfig'.
(Details: serial 31 error_code 178 request_code 155 minor_code 34)
(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.)
Erreur de segmentation (core dumped)
The backtrace being:
#0 0x0822020c in GSFrame:

#1 0x081dcb20 in Pcsx2App::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) ()
#2 0x081dcadd in Pcsx2App::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) const ()
#3 0xf7f20808 in wxEvtHandler:

#4 0xf7f20be4 in wxEvtHandler:

#5 0xf7f20cbe in wxEvtHandler:

#6 0xf7ceed12 in wxTimerBase::Notify() () from /usr/lib32/libwx_gtk2u_core-2.8.so.0
#7 0xf7be912a in ?? () from /usr/lib32/libwx_gtk2u_core-2.8.so.0
#8 0xf6e14bb1 in ?? () from /usr/lib32/libglib-2.0.so.0
#9 0xf6e14097 in g_main_context_dispatch () from /usr/lib32/libglib-2.0.so.0
#10 0xf6e14458 in ?? () from /usr/lib32/libglib-2.0.so.0
#11 0xf6e14753 in g_main_loop_run () from /usr/lib32/libglib-2.0.so.0
#12 0xf73cba75 in gtk_main () from /usr/lib32/libgtk-x11-2.0.so.0
#13 0xf7bde9d3 in wxEventLoop::Run() () from /usr/lib32/libwx_gtk2u_core-2.8.so.0
#14 0xf7c6f584 in wxAppBase::MainLoop() () from /usr/lib32/libwx_gtk2u_core-2.8.so.0
#15 0xf7c6f0e0 in wxAppBase:

#16 0xf7ebe706 in wxEntry(int&, wchar_t**) () from /usr/lib32/libwx_baseu-2.8.so.0
#17 0xf7ebe7a3 in wxEntry(int&, char**) () from /usr/lib32/libwx_baseu-2.8.so.0
#18 0x081db87b in main ()
Hope it helps, but, I try to use the debugger to see what causes the bug on gsdx but it fails miserably before I get read anything meaningful. I guess it's related to something in the problem right... But not fully sure either.
Laptop: Arch Linux x86_64
CPU :Core i3-3217U @ 1.8Ghz
GPU: intel HD4000
4GO RAM DDR3-1600Mhz
Desktop: Arch Linux x86_64
CPU : Core i7 2600k @ 4.1Ghz
GPU : Nvidia GTX 770 OC Gigabyte
8GO Ram dual channel DDR3-1600 Mhz
CPU :Core i3-3217U @ 1.8Ghz
GPU: intel HD4000
4GO RAM DDR3-1600Mhz
Desktop: Arch Linux x86_64
CPU : Core i7 2600k @ 4.1Ghz
GPU : Nvidia GTX 770 OC Gigabyte
8GO Ram dual channel DDR3-1600 Mhz