Re: gnus crashes XEmacs (on MacOS X 10.0.1) in summary buffer
Hi,
Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes:
> > Program received signal EXC_BAD_ACCESS, Could not access
memory.
^^^^^^^^^^^^^^
what kind of a signal is that? is that like a SEGV?
Sort of, it an exception raised by the mach kernel. It's somehow
confusing, because normally the UNIX server converts mach kernel
exceptions to UNIX signals...
I found a little hint in /usr/include/mach/exception_types.h:
#define EXC_BAD_ACCESS 1 /* Could not access memory */
/* Code contains kern_return_t describing error. */
/* Subcode contains bad memory address. */
maybe you are hitting a limit of the size of the stack similar to
what we often see on DEC OSF and OpenBSD. See the following entry
from our PROBLEMS file.
what is the default stack size on your OS?
Hmmm... I don't know... How can I find out?
The information on stack size limit (in bytes) I found was in der
kernel sources, but I'm almost sure that this not the answer to your
question?
#define MAXSSIZ (64*1024*1024) /* max stack size */
| 2) Recompile regex.c with REGEX_MALLOC defined.
Okay, I will try that, that seems to be easy. ;-)
Ciao,
Eric
--
"Excuse me --- Di Du Du Duuuuh Di Dii --- Huh Weeeheeee" (Albert King)