[Bug 251257] sysutils/fluent-bit: Fix for SIGSEGV with SEGV_MAPERR code for the version 1.6.4

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Nov 19 15:53:26 UTC 2020


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251257

            Bug ID: 251257
           Summary: sysutils/fluent-bit: Fix for SIGSEGV with SEGV_MAPERR
                    code for the version 1.6.4
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: girgen at FreeBSD.org
          Reporter: ard_1 at mail.ru
             Flags: maintainer-feedback?(girgen at FreeBSD.org)
          Assignee: girgen at FreeBSD.org

Created attachment 219815
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219815&action=edit
Patch for the ports tree to build fixed version from upstream master branch

Fluent-bit 1.6.4 have some memory allocation problems that were fixed in
upstream master branch but as of time of this writing were not included in any
tagged release.
The attached patch will build fluent-bit at commit b7c7081 from the github
master branch that seems to include a fix for this problem.

Since I usually opt out for using untagged upstream code in non-development
versions of ports in the FreeBSD ports tree, I think that this patch should not
be committed in the FreeBSD ports tree.
It is provided just to help others who is facing this issue to quickly build a
patched version using their own copy of the FreeBSD ports tree.


truss utility output for this issue will be similar to this output:

write(10,"o\0\0\0\0\0\0\0\^[[1m[\^[[0m2020"...,4096) = 4096 (0x1000)
select(14,{ 7 9 11 13 },{ },0x0,0x0)             = 1 (0x1)
read(9,"o\0\0\0\0\0\0\0\^[[1m[\^[[0m2020"...,4096) = 4096 (0x1000)
SIGNAL 11 (SIGSEGV) code=SEGV_MAPERR trapno=12 addr=0x800a1b028
sigprocmask(SIG_SETMASK,{ SIGSEGV },0x0)         = 0 (0x0)
write(2,"\^[[1m[\^[[0m2020/11/17 02:19:56"...,111) = 111 (0x6f)
write(2,"[2020/11/17 02:19:56] ",22)             = 22 (0x16)
write(2,"[engine] caught signal (",24)           = 24 (0x18)
write(2,"SIGSEGV)\n",9)                          = 9 (0x9)
write(2,"ERROR: no stack trace because un"...,62) = 62 (0x3e)
sigprocmask(SIG_SETMASK,{
SIGHUP|SIGINT|SIGQUIT|SIGILL|SIGTRAP|SIGEMT|SIGFPE|SIGKILL|SIGBUS|SIGSEGV|SIGSYS|SIG
PIPE|SIGALRM|SIGTERM|SIGURG|SIGSTOP|SIGTSTP|SIGCONT|SIGCHLD|SIGTTIN|SIGTTOU|SIGIO|SIGXCPU|SIGXFSZ|SIGVTALRM|SI
GPROF|SIGWINCH|SIGINFO|SIGUSR1|SIGUSR2 },0x0) = 0 (0x0)
thr_self(0x801ccc1e0)                            = 0 (0x0)
thr_kill(100821,SIGABRT)                         = 0 (0x0)
SIGNAL 6 (SIGABRT) code=SI_LWP pid=47105 uid=0
select(14,{ 7 9 11 13 },{ },0x0,0x0)             ERR#4 'Interrupted system
call'

The backtrace in lldb output will be similar to this:
lldb -c ./fluent-bit.core -- fluent-bit
(lldb) target create "fluent-bit" --core "./fluent-bit.core"
Core file '/home/ard/work/flb164/fluent-bit.core' (x86_64) was loaded.
(lldb) thread backtrace all
* thread #1, name = 'fluent-bit', stop reason = signal SIGABRT
  * frame #0: 0x000000080131f0fa
    frame #1: 0x000000080131f0c4
  thread #2, name = 'fluent-bit', stop reason = signal SIGABRT
    frame #0: 0x000000080133ebca
    frame #1: 0x000000080103c9dc
  thread #3, name = 'fluent-bit', stop reason = signal SIGABRT
    frame #0: 0x00000008013ad8da
    frame #1: 0x000000080103cd92
    frame #2: 0x00000000006d3198
fluent-bit`___lldb_unnamed_symbol2349$$fluent-bit + 200
    frame #3: 0x000000000043692a fluent-bit`___lldb_unnamed_symbol9$$fluent-bit
+ 58
    frame #4: 0x000000000044bf60
fluent-bit`___lldb_unnamed_symbol20$$fluent-bit + 192
  thread #4, name = 'fluent-bit', stop reason = signal SIGABRT
    frame #0: 0x000000080133ebca
    frame #1: 0x000000080103c9dc
    frame #2: 0x00000000006d28f8 fluent-bit`cio_stream_delete + 8
  thread #5, name = 'fluent-bit', stop reason = signal SIGABRT
    frame #0: 0x000000080133ebca
    frame #1: 0x000000080103c9dc
    frame #2: 0x00000000006d28f8 fluent-bit`cio_stream_delete + 8
  thread #6, name = 'fluent-bit', stop reason = signal SIGABRT
    frame #0: 0x000000080133ebca
    frame #1: 0x000000080103c9dc
    frame #2: 0x00000000006d28f8 fluent-bit`cio_stream_delete + 8
  thread #7, name = 'fluent-bit', stop reason = signal SIGABRT
    frame #0: 0x000000080133ebca
    frame #1: 0x000000080103c9dc
    frame #2: 0x00000000006d28f8 fluent-bit`cio_stream_delete + 8

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list