Rolling back to a specfic build.
#61
check the gui where it get the plugins. Normally you must get $HOME/build/svn/pcsx2-git/bin/plugins
Reply

Sponsored links

#62
That is where it says they are suppose to be, and that is indeed where they are.
i7 4930k @4.3, 4x4 GB RAM @2133 (15-15-15-27, quad channel), EVGA 570 @stock, Arch 64b.
Reply
#63
And what the emuLog.txt file is saying.
Reply
#64
(03-30-2014, 03:13 PM)gregory Wrote: And what the emuLog.txt file is saying.

Code:
PCSX2 1.3.0-20140326113749  - compiled on Mar 30 2014
Savestate version: 0x9a0a0000

Host Machine Init:
    Operating System =  Linux 3.13.7-1-ARCH x86_64
    Physical RAM     =  7929 MB
    CPU name         =  Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz
    Vendor/Model     =  GenuineIntel (stepping 04)
    CPU speed        =  3.396 ghz (12 logical threads)
    x86PType         =  Standard OEM
    x86Flags         =  bfebfbff 7fbee3bf
    x86EFlags        =  2c100000

x86 Features Detected:
    MMX.. SSE.. SSE2.. SSE3.. SSSE3.. SSE4.1.. SSE4.2.. AVX

Installing POSIX SIGSEGV handler...
Reserving memory for recompilers...
[wx] iCCP: Not recognizing known sRGB profile that has been edited

Loading plugins...
    Binding   GS: /tmp/pcsx2-git/bin/plugins/libGSdx-0.1.16.so
    Binding  PAD: /tmp/pcsx2-git/bin/plugins/libonepad-1.1.0.so
    Binding SPU2: /tmp/pcsx2-git/bin/plugins/libspu2x-2.0.0.so
    Binding CDVD: /tmp/pcsx2-git/bin/plugins/libCDVDiso.so
    Binding  USB: /tmp/pcsx2-git/bin/plugins/libUSBnull-0.7.0.so
    Binding   FW: /tmp/pcsx2-git/bin/plugins/libFWnull-0.7.0.so
    Binding DEV9: /tmp/pcsx2-git/bin/plugins/libdev9null-0.5.0.so
Plugins loaded successfully.

(GameDB) 9653 games on record (loaded in 192ms)
    HotSwapping to new ISO src image!
HLE Notice: ELF does not have a path.


Initializing plugins...
    Init GS
    Init PAD
    Init SPU2
    Init CDVD
    Init USB
    Init FW
    Init DEV9
Plugins initialized successfully.

Opening plugins...
    Opening GS
i7 4930k @4.3, 4x4 GB RAM @2133 (15-15-15-27, quad channel), EVGA 570 @stock, Arch 64b.
Reply
#65
Maybe you linked against some wrong library. You can check the link with "ldd" command. For example ldd pcsx2 or ldd /tmp/pcsx2-git/bin/plugins/libGSdx-0.1.16.so

Check it is really used wx2.8.

Otherwise use gdb to get a backtrace:
gdb ./bin/pcsx2
#run
>start
>backtrace
Reply
#66
"ldd /tmp/pcsx2-git/bin/plugins/libGSdx-0.1.16.so |grep wx" returns nothing. Nothing is linking to wx.

As for gdb:

Code:
$ gdb ./pcsx2
GNU gdb (GDB) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
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 "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./pcsx2...(no debugging symbols found)...done.
(gdb) #run
(gdb) >start
Undefined command: ">start".  Try "help".
(gdb) start
Temporary breakpoint 1 at 0x81f0c53
Starting program: /tmp/pcsx2-git/bin/pcsx2
warning: Could not load shared library symbols for linux-gate.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

Temporary breakpoint 1, 0x081f0c53 in main ()
(gdb) backtrace
#0  0x081f0c53 in main ()
(gdb)
i7 4930k @4.3, 4x4 GB RAM @2133 (15-15-15-27, quad channel), EVGA 570 @stock, Arch 64b.
Reply
#67
ZWell the idea was to check pcsx2. For gdb, don't put the prompt char Wink (yes it was not clear)

Edit:backtrace after the crash!
Reply
#68
okay, so what I need to do is run PCSX2, then run gdb, then type start then make PCSX2 crash, then run backtrace?

I've never used, or even heard of, gdb before today so this is a bit new.

Also, can this help me debug my python scripts? I'm decent when it comes to putting together code that should work, but when it comes times to figure out why it doesn't work, I'm lost.
i7 4930k @4.3, 4x4 GB RAM @2133 (15-15-15-27, quad channel), EVGA 570 @stock, Arch 64b.
Reply
#69
Yes

No for python.
Reply
#70
I did as I said I would do in my last post and the gdb output appears to be exactly the same as the last time I tried. I'm not sure I'm doing this correctly.

Code:
$ gdb ./pcsx2
GNU gdb (GDB) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
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 "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./pcsx2...(no debugging symbols found)...done.
(gdb) start
Temporary breakpoint 1 at 0x81f0c53
Starting program: /tmp/pcsx2-git/bin/pcsx2
warning: Could not load shared library symbols for linux-gate.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

Temporary breakpoint 1, 0x081f0c53 in main ()
(gdb) backtrace
#0  0x081f0c53 in main ()
i7 4930k @4.3, 4x4 GB RAM @2133 (15-15-15-27, quad channel), EVGA 570 @stock, Arch 64b.
Reply




Users browsing this thread: 2 Guest(s)