🚀 go-pugleaf

>--  Why would interrupting a program during startup result in an illegal
>instruction signal?

See below.

>--  What do the log messages mean?

See below.

>--  Why does the log message say "sig=11" (segmentation fault), but
>"Illegal instruction", (signal 4), is printed on my terminal.

Because:

	1) "bash" is catching SIGSEGV;

	2) it did something that caused a SIGSEGV when you ^C'ed it;

	3) the user stack pointer was bad (the address 0xffffffdc looks
	   bogus), so the kernel couldn't deliver the SIGSEGV to the
	   process (it has to push stuff onto the stack to do so);

	4) if that happens, the kernel sends a SIGILL to the process to
	   kill it off, and logs some messages to indicate why it's
	   doing so.

Could be a bug somewhere in "bash"....