[DGD] Error with 1.5.5

[Raymond Jennings]

If you *were* able to reproduce a true segfault (and not just an abort), a
stack trace would be helpful.

Do make sure it's not due to an infinite recursion though.

On Sun, Jul 16, 2017 at 11:24 PM, Felix A. Croes <felix at dworkin.nl> wrote:

> Blain <blain20 at gmail.com> wrote:
>
> > I triggered a segfault after compile_error and before runtime_error are
> > called in the driver object.  I created a bare bones implementation and
> > determined that the following does bug out.
> >
> > [/driver.c]
> > void initialize() {
> >   call_out("load_foo");
> > }
> >
> > void load_foo() {
> >   compile_object("/foo");
> > }
> >
> > [/foo.c]
> > void foo() {
> >   test = ({});
> > }
> >
> > Also, /auto.c and /auto.h are empty files.
> >
> > With the variable test not being declared in foo.c, DGD segfaults.  The
> > error message given to compile_error is "undeclared variable test".
>
> The errormessage I get is "/driver.c, 2: too few arguments for function
> call_out".
>
> After fixing that, a fatal error: "missing function in driver object:
> compile_error", which does crash DGD, not with a segmentation fault
> but with an abort call.  That is proper and expected behaviour.
>
> Regards,
> Felix Croes
> ____________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd