[m-dev.] strange segmentation violations

[Ian MacLarty]

On Tue, Mar 14, 2006 at 12:02:22AM +1100, Julien Fischer wrote:
> 
> On Mon, 13 Mar 2006, Ian MacLarty wrote:
> 
> > Hello,
> >
> > On Cygwin it seems that users get the message "caught strange
> > segmentation violation" when the stack overflows.
> >
> > The code that prints this message is in mercury_memory_handlers.c, in the
> > function complex_segvhandler and looks like the following:
> >
> >     if (sig != SIGSEGV || !info || info->si_signo != SIGSEGV) {
> >         fprintf(stderr, "\n*** Mercury runtime: ");
> >         fprintf(stderr, "caught strange segmentation violation ***\n");
> >         exit(1);
> >     }
> >
> > Could it be that sig or info are being set differently on Cygwin and
> > that is why the normal segfault message for stack overflow is not being
> > printed?  Also why is no stack dump or trace report printed when this
> > seg fault occurs?
> 
> What grade is the program compiled in?
> 

asm_fast.gc.decldebug
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------