Maybe, or maybe not.  I wasn't looking at the panicked machine's console
at that time, so I'm not sure if it was ctrl+C that triggered the panic,
or it was already dumping the kernel memory when I hit ctrl+C.  Or it
could be SIGWINCH which triggered it.  In any case, the panic is not
easy to reproduce.  I also saw a complete lock up (no ctrl+alt+esc) when
I slogin'ed to this machine yesterday, but I'm not sure if it's related
to this problem at all.

I took a quick look at source code, and it seemed it didn't.
In case you can't find it elsewhere, here's the one:
  http://122.249.219.233/distfiles/w3m-0.5.2.tar.gz

If I run above code and hit ctrl+C, the program terminates.  If I change
it to mask SIGINT, it ignores ctrl+C until connection times out, and in the
following iterations connect() fails immediately.  Hmm...

Thanks.