Results 1 to 2 of 2
Hello, I'm running vanilla 126.96.36.199 on Pentium-M with busybox 1.14.2 At a specific scenario the application is causing linux to crash. How can I debug this ? After the crash, ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 07-03-2012 #1
- Join Date
- Aug 2007
188.8.131.52: Application causes linux to crash
I'm running vanilla 184.108.40.206 on Pentium-M with busybox 1.14.2
At a specific scenario the application is causing linux to crash.
How can I debug this ?
After the crash, the console is not active any more.
I also tried using ttyS1 as console (RS232) but the kernel messages does not give a clue.
When I tried a smaller kernel I get other messages (I removed unnecessary drivers).
I tried using duma.
On the init phase, there are thousands of dynamic allocations and this is causing the init phase to run forever. The console is active and the CPU usage is almost 100%.
With dmalloc, the init phase does not start and CPU usage is 0%.
What other tools can I use ?
- 07-06-2012 #2
- Join Date
- Apr 2009
- I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
After you reboot, see what dmesg shows, as well as /var/log/messages*Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!