Helping understand cause of SIGSEGV

[Pete Wright]

On 11/7/20 4:12 PM, Pete Wright wrote:
>
>
>
> thanks for your help on the Patrick - i suspect to make much more 
> progress i'll need someone from the fluent-bit team to take a closer 
> look as to what's happening.
>

Just to revive this thread, Artyom Davidov was nice enough to chime in 
on the freebsd bug i filed for this 
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250825) and we made 
some progress.  it looks like the SIGSEGV is only reproducible on 12.x 
and newer FreeBSD builds - he is unable to reproduce the issue on his 
11.4 system.

I guess my next question I'll need to answer is what major changes 
happened b/w 11 and 12 that could trigger this error.  At first I was 
wondering if it was an issue with llvm, but this port is built using 
gcc, so that helps narrow the gap a little bit.  i reckon it's also good 
that we at least have a version of freebsd that is functional, so there 
is a reference point to start from.

since it is looking like a threading issue perhaps i should start 
splunking around that area...unless others have some good hints.

-pete

-- 
Pete Wright
pete at nomadlogic.org
@nomadlogicLA