[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
more on -> Re: [ale] segmentation fault.............
I have always been able to debug SEGFAULTs by:
- Checking application and system logfiles
- Comparing library versions with a known working system
- strace'ing the process to get an idea of the bad behavior (what system
calls are executed up to the problem area)
- Compiling the software with "-ggdb -d" so I can get the line of code
causing the problems. If this isn't an option, a disassembler can help.
- Run the program within gdb to determine WHERE (based on the call tree
and the stack frame during the crash) the crash is occurring
- If the code is easy enough to debug, I usually follow the logic with
paper and pencil or dump the stack backtrace into deja.com/google.com/mailing list archives
Let me know if I can help further,
On Sun, 25 Jan 2004, Courtney Thomas wrote:
> Just tried it again and got........
> Kernel Panic
> Thanks for any help.
> Courtney Thomas wrote:
> > Attempting to tape [/dev/nst0] backup a harddrive [/dev/sda5] using the
> > command.....
> > dump 0af /dev/nst0 /dev/sda5
> > under Debian-2.4.17, I am getting crashes with screen errors such
> > as..........
> > Init ID "2" : respawning too fast, disabled for 5 min
> > segmentation fault
> > as well as screens full of Code so and so, and lots of other stuff !
> > What's the probable problem and cure ?
> > Appreciatively,
> Courtney Thomas
> s/v Mutiny
> lying Oriental, NC
> Ale mailing list
> Ale at ale.org
Ryan Matteson - UNIX Administrator | GPG ID: 92D5DFFF
Public Key: http://www.daemons.net/~matty/public_key.txt
Fingerprint = 4BEC 6145 30A6 BCE6 5602 FF11 4954 165D 92D5 DFFF