Menu and Text will not show up
#51
Thanks.
I installed "pcsx2-unstable-dbg" but nothing changed.
With "ps aux | grep pcsx2", I got this two lines:
Code:
4853 5.7 2.9 694120 117640 pts/1 Sl+
4934 0.0 0.0 14620  944    pts/3 S+
Reply

Sponsored links

#52
It is because PCSX2 isn't running. PCSX2 must run otherwise the process don't exists.
Reply
#53
I tried all the ways, running, not running, crashing...
I realized the values shown with "ps aux | grep pcsx2" change and are different if I run the command while running, not running, crashing, running again...
Notice I write and do all this having no idea and as complete noob.
Reply
#54
take 2 terminal:
In the first one run pcsx2.
# pcsx2
play the game until the crash. And don't close any pcsx2 windows.

In terminal 2, get the current process
Or you can use the command "top" or any system task viewever. (google get process id linux)
Code:
ps aux | grep pcsx2
Here the result on my system:
gregory 3989 0.0 0.3 582872 18752 ? Sl 2013 8:26 xfce4-terminal --geometry=200x67 --display :0.0 --role=xfce4-terminal-1384166181-1995588460 --show-menubar --show-borders --hide-toolbar --working-directory /home/gregory/playstation
gregory 18708 6.2 0.9 492908 60380 pts/9 Sl+ 18:31 0:00 ./pcsx2-dbg
gregory 18725 0.0 0.0 10288 868 pts/7 S+ 18:31 0:00 grep pcsx2
Reply
#55
Game crashes after launch with full white screen, error message popping up.
For "ps aux | grep pcsx2", I got the mentioned...
Code:
5450  0.5  2.9 694092 117700 pts/1   Sl+
5613  0.0  0.0  14620   944 pts/3    S+
Running "ps aux | grep pcsx2-dbg", it is the same...
Code:
5619  0.0  0.0  14620   948 pts/3    S+
Running "ps aux | grep pcsx2 -i", again the same...
Code:
5704  0.9  2.9 694112 117644 pts/1   Sl+
5851  0.0  0.0  14620   952 pts/3    S+
Reply
#56
try ps aux | grep pcsx2 -i
maybe it is an issue with the case. Otherwise use top. You will see all process of your system (use "shift m" to sort them by memory usage)
Reply
#57
Maybe I didn't understand well, do you want me to get the pid of the pcsx2 process and then make me do something with it?
I already got the pid as you told me, but then do I do something more?
Reply
#58
If you have the pid, just run gdb like that
gdb + name_of_executable + pid
for example:
gdb pcsx2 316
If it work well it will freeze PCSX2 windows. Then just dump the backtrace "thread apply all bt full"
Reply
#59
Thanks for your patience.
It is my fault that I am not being able to do this properly, something in my system configuration or something I am doing wrong, because despite I installed "pcsx2-unstable-dbg" (synaptic description says it has the debug symbols), when I run "gdb pcsx2 pid", it insists the debug symbols can't be found.
I will try to check and see if I can come with the info.
Thanks.
Reply
#60
Forget about the message and try to generate the backtrace. I will tell you if you miss somethings (post all gdb transcript)
Reply




Users browsing this thread: 1 Guest(s)