| |
Core Crash Stack Trace For Flash Media Server On Linux
By: Stefan Richter
Expert Author
2007-10-02
As promised previously here are some instructions on how to create a stack trace for FMS on Linux.
Thanks to Asa Whillock from Adobe for writing this up.
1. Go to your installed FMS directory
2. You should see in this directory something like core.#### where #### is the PID of the crashed process.
3. If you don't see core.#### after the crash, likely you have core dumps turned off so that Linux didn't make one when you crashed.
3a. Edit your 'server' file in the same FMS install dir. Add the line 'ulimit -c unlimited' following the other ulimits in the first few lines. Then run and crash again.
4. Write a new file - it's a batch file for gdb. I called mine stackTracer
5. In this new file insert only two lines
thread apply all bt
quit
6. Save and close the file
7. Run the following command in the same dir
Gdb fmscore -batch -c core.#### -x stackTracer > stackOutput
Now you should have a file named stackOutput that when you open it has a stack trace with all the threads and symbols that can be taken from fmscore when it crashed. If you get a file with mostly ?? for the right side of the stacks it might not be the right file so check what crashed - it might not have been the fmscore.
That's a good start point for narrowing down any problems with a crashing FMS.
Comments
About the Author:
Stefan is a certified Flash Developer who has been involved with Flash Media
Server since its very early days. From his home office in the UK he has
handled a variety of projects, specializing in Flash Video and Rich Internet
Applications for clients that include CNET, USA Network and Unilever. Stefan
is the author of a series of Adobe Developer Center articles, has spoken at
several industry events and contributes a regular column on Flash Video to
Streaming Media Magazine. His site www.flashcomguru.com is one of the
largest online resources on Flash Video.
|
|
