Re: [Bug: 21.5-b29] Syntactic font-lock confuses skip-syntax-forward
On Thu, Apr 28, 2011 at 9:29 PM, Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
> Especially the macros seem scary. It doesn't help that
running my
> self-compiled XEmacs under GDB (Ubuntu) will segfault in
> memset()...
Can you give us a backtrace for that?
The segfault is due to this:
> Using the new incremental garbage collector and the new
allocator.
That activates the virtual dirty bit code, which uses deliberate
SIGSEGV/SIGBUS signals to manage memory. Do this:
(gdb) handle SIGSEGV nostop noprint pass
(gdb) handle SIGBUS nostop noprint pass
Regards,
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta