[DGD] Segfault

[Raymond Jennings]

Of note, this also helps when I get a craw biter in atomic_error, which
helps when I can't use file based logging.

On Thu, May 19, 2016 at 7:00 AM, Raymond Jennings <shentino at gmail.com>
wrote:

> Ahh...so it was an infinite recursion after all.
>
> First of all...never mind the bug report.
>
> Second of all...I have a trick to catch problems like that.  Wrap your
> whole error handler in a catch, and in the handler section just spit out a
> simple message to the console.
>
> If you can steal the stack trace reporter from the kernel library's driver
> object you can also spit that out to console too.
>
> On Thu, May 19, 2016 at 6:57 AM, Blain <blain20 at gmail.com> wrote:
>
>> Yep.  My error service was bugging while compiling the trace text.  When
>> fixed, I found that the static function being called was causing an error
>> because I'm capturing its return in an int and throwing an error about the
>> return value not being int.  Then the error service went into a loop
>> reporting its own internal error.  Good call.
>>
>> On Thu, May 19, 2016 at 8:17 AM, Blain <blain20 at gmail.com> wrote:
>>
>> > It segfaults at the callother with the function being static, and works
>> > fine with the function not being static.  It's possible that the error
>> > messaging is getting stuck in a loop, though.  I'll have to track that
>> down.
>> > On May 19, 2016 8:02 AM, "Raymond Jennings" <shentino at gmail.com> wrote:
>> >
>> >> That shouldn't cause a segfault though.
>> >>
>> >> Calling a static function in another object should at most fail
>> silently
>> >> with a nil return value.
>> >>
>> >> If you can run the core dump through gdb and generate a stack trace you
>> >> should send it to dworkin.
>> >>
>> >> The only reason dgd should crash is infinite recursion.
>> >> ____________________________________________
>> >> https://mail.dworkin.nl/mailman/listinfo/dgd
>> >
>> >
>> ____________________________________________
>> https://mail.dworkin.nl/mailman/listinfo/dgd
>>
>
>