@@ -130,6 +130,29 @@ $ valgrind --tool=memcheck --leak-check=full radiusd -Xm cannot do anything about those problems. However, any errors that are inside of the FreeRADIUS source should be brought to our attention. + +6. Running with "screen" + + If the bug is a crash of the server, and it takes a long time for the + crash to happen, perform the following steps: + + * log in as root + * open a screen session (http://blogamundo.net/code/screen/) + $ screen bash + * make sure FreeRADIUS is not running + * make sure you have all the debug symbols about, or a debugable + version of the server installed + * configure screen to log to a file; 'Ctrl-A H' + * type 'gdb /path/to/radius' (or /path/to/freeradius on Debian) + * at the (gdb) prompt, type 'run -X' + * detach from screen 'Ctrl-A D' + * when you notice FreeRADIUS has died, reconnect to your screen session + $ screen -D -r + * at the (gdb) prompt type 'where' or for *lots* of info try + 'thread apply all bt full' + * tell screen to stop logging, 'Ctrl-A H' + * logout from screen + -- FreeRADIUS Project, copyright 2008 doc/bugs fb12a47d98e6bf919243f83180b95a9624166203 Alan T. DeKok aland@freeradius.org http://github.com/Antti/freeradius-server/commit/82188f7ec3ad2793467e358fecd90d214008dffe 82188f7ec3ad2793467e358fecd90d214008dffe 2009-01-12T01:16:34-08:00 2009-01-07T01:51:34-08:00 Added notes on using "screen" f05f4e02b107338ea666eb2c6749ed86ee650216 Alan T. DeKok aland@freeradius.org