Jump to content

  • Log In with Google      Sign In   
  • Create Account


#Actualpolyfrag

Posted 31 December 2012 - 06:19 PM

It just crashed with valgrind and it didn't say there were any memory leaks.

 

It seems it crashes whenever my open SSH session gets closed by me closing the laptop or leaving it on until it goes to sleep.

 

I thought I had turned on core dump following these instructions

 

http://www.cyberciti.biz/tips/linux-core-dumps.html

 

but I don't see anything in /tmp.

So to run it under gdb I type in
 

gdb myProgram
run


But since I'm doing this remotely from an SSH shell I need it to fork the process and output to a file. How do I do that? I need it to continue running after I end the SSH session.

I can't just do

 

 

gdb myProgram &


because I need to type in "run" to gdb.


#4polyfrag

Posted 31 December 2012 - 06:12 PM

It just crashed with valgrind and it didn't say there were any memory leaks.

 

I thought I had turned on core dump following these instructions

 

http://www.cyberciti.biz/tips/linux-core-dumps.html

 

but I don't see anything in /tmp.

So to run it under gdb I type in
 

gdb myProgram
run


But since I'm doing this remotely from an SSH shell I need it to fork the process and output to a file. How do I do that? I need it to continue running after I end the SSH session.

I can't just do

 

 

gdb myProgram &


because I need to type in "run" to gdb.


#3polyfrag

Posted 31 December 2012 - 06:09 PM

It just crashed with valgrind and it didn't say there were any memory leaks.

So to run it under gdb I type in

gdb myProgram
run

But since I'm doing this remotely from an SSH shell I need it to fork the process and output to a file. How do I do that? I need it to continue running after I end the SSH session.

I can't just do

gdb myProgram &

because I need to type in "run" to gdb.

#2polyfrag

Posted 31 December 2012 - 06:08 PM

It just crashed with valgrind and it didn't say there were any memory leaks.

So to run it under gdb I type in

gdb myProgram
run

But since I'm doing this remotely from an SSH shell I need it to fork the process and output to a file. How do I do that? I need it to continue running after I end the SSH session.

I can't just do

gdb myProgram &

because I need to type in "run" to gdb.

#1polyfrag

Posted 31 December 2012 - 06:03 PM

It just crashed with valgrind and it didn't say there were any memory leaks.

 

So to run it under gdb I type in

 

gdb myProgram

run

 

But since I'm doing this remotely from an SSH shell I need it to fork the process and output to a file. How do I do that? I need it to continue running after I end the SSH session.


PARTNERS