process gets a SIGSEGV: how to find out where?

[jay dubb]

   I am posting this for a friend of mine who doesn't have access
to USENET, so please respond directly to mlevin at jade.tufts.edu.

   I have a process that for some reason receives a SIGSEGV signal. It
does not dump core, however. What is the best way to find out which
function caused this? If there was a core file generated, I could use
a debugger, but it does not create one. Is there any way I can force
it to dump core on SIGSEGV, so that I can find out where it was when
this happenned? Perhaps there is a way to find out, if I trap it using
a signal handler or something. Any ideas? Thanks in advance.

					Mike Levin (mlevin at jade.tufts.edu)