Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On my embedded device, I have this error showing up after kernel boot:

init.exe: Caught segmentation fault, core dumped

But I cannot understand why is this happening? If I do battery cut( i.e. reboot my device foricbly) then the device boots and comes up fine.

Any pointers will be extremely helpful. Is this some transient low level memory issue?

It is linux 2.6.31 on Arm architecture.

share|improve this question
Nowhere near enough information. What Unix is this? What type of init is this? What is the device? – Chris Down Mar 28 '12 at 23:37
Sorry, but there is not nearly enough information to answer this question. There probably is something wrong with your firmware, or with your software (maybe it's not initializing memory properly and picking up some old garbage that's set to a safe bit pattern upon reset), or even with your hardware. Good luck with debugging. – Gilles Mar 28 '12 at 23:41
And why on earth is it named init.exe? .exe is for Windows. – psusi Mar 29 '12 at 17:09
up vote 1 down vote accepted

The output mentions it dumped core. Try doing:

gdb -c [corefile]

Then at the (gdb) prompt, do:

(gdb) bt

To get a backtrace. If the binary was not stripped, you might be in luck and at least have something to google for :-)

PS: The core file might be core.PID, where PID was the PID of init.exe when it died.


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.