[DGD] status() O_CALLOUTS overflow

[Raymond Jennings]

"short" sighted was a pun by the way.

On Tue, Sep 11, 2018 at 10:23 AM Raymond Jennings <shentino at gmail.com>
wrote:

> More like a short sighted design decision in Kotaka.
> On Tue, Sep 11, 2018 at 7:06 AM <bart at wotf.org> wrote:
> >
> > Either you have max array size set quite low, or you found a reason to
> > generate even more call_outs in a single object than I ever managed..
> torture
> > test time?
> >
> > Bart.
> >
> > On Tue, 11 Sep 2018 05:24:29 -0700, Raymond Jennings wrote
> > > This just caused a nasty runtime error in the kernel library :P
> > > On Tue, Sep 11, 2018 at 3:10 AM <bart at wotf.org> wrote:
> > > >
> > > > in data.cpp, in d_list_callouts:
> > > >
> > > >     if (count > conf_array_size()) {
> > > >         return (Array *) NULL;
> > > >     }
> > > >
> > > > So, the code says yes, and that doesn't look like an accident :-)
> > > >
> > > > Bart.
> > > >
> > > > On Tue, 11 Sep 2018 00:38:30 -0700, Raymond Jennings wrote
> > > > > Just curious, is DGD supposed to return nil for O_CALLOUTS if the
> > > > > number of callouts in an object exceeds the maximum array size?
> > > > > ____________________________________________
> > > > > https://mail.dworkin.nl/mailman/listinfo/dgd
> > > >
> > > >
> > > > --
> > > > https://www.bartsplace.net/
> > > > https://wotf.org/
> > > > https://www.flickr.com/photos/mrobjective/
> > > >
> > > > ____________________________________________
> > > > https://mail.dworkin.nl/mailman/listinfo/dgd
> > > ____________________________________________
> > > https://mail.dworkin.nl/mailman/listinfo/dgd
> >
> >
> > --
> > https://www.bartsplace.net/
> > https://wotf.org/
> > https://www.flickr.com/photos/mrobjective/
> >
> > ____________________________________________
> > https://mail.dworkin.nl/mailman/listinfo/dgd
>