Posts: 6.069
Threads: 68
Joined: May 2010
Reputation:
167
Location: Grenoble, France
01-04-2014, 07:21 PM
(This post was last modified: 01-04-2014, 07:21 PM by gregory.)
It is because PCSX2 isn't running. PCSX2 must run otherwise the process don't exists.
Posts: 55
Threads: 1
Joined: Dec 2013
Reputation:
0
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.
Posts: 6.069
Threads: 68
Joined: May 2010
Reputation:
167
Location: Grenoble, France
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)
Posts: 55
Threads: 1
Joined: Dec 2013
Reputation:
0
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?
Posts: 6.069
Threads: 68
Joined: May 2010
Reputation:
167
Location: Grenoble, France
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"
Posts: 55
Threads: 1
Joined: Dec 2013
Reputation:
0
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.
Posts: 6.069
Threads: 68
Joined: May 2010
Reputation:
167
Location: Grenoble, France
Forget about the message and try to generate the backtrace. I will tell you if you miss somethings (post all gdb transcript)