search for: __strlen_sse2_pminub

...oveadm.debug...done. done. [New LWP 2418] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `doveadm replicator replicate -f'. Program terminated with signal 11, Segmentation fault. #0 0x00007fd2c059f921 in __strlen_sse2_pminub () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.6-13.el7.x86_64 glibc-2.17-196.el7.x86_64 nss-softokn-freebl-3.28.3-8.el7_4.x86_64 xz-libs-5.2.2-1.el7.x86_64 zlib-1.2.7-17.el7.x86_64 (gdb) bt full #0 0x00007fd2c059f921 in __strlen_sse2_pminub () from...

...ction and the name moved as well, that's not the same as keeping the same function as far as debug info metadata is concerned) > I compile this with '-O0 -g'. A 'break main'/'run'/'break strlen'/'cont' > gives a relevant stack trace: > > #0 __strlen_sse2_pminub () at > ../sysdeps/x86_64/multiarch/strlen-sse2-pminub.S:33 > #1 0x00005555555587ff in __dfsw_strlen (s=0x55555556fe17 "foo", > s_label=<optimized out>, ret_label=0x7fffffffddee) > at llvm/projects/compiler-rt/lib/dfsan/dfsan_custom.cc:203 > #2 0x000055555556bbd...

...ct(Sys.time(), format = "%H%M") 6: format(Sys.time(), format = "%H%M") 7: format(Sys.time(), format = "%H%M") ? ? I looked into the dumped core with gdb, and found something very strange: gdb /usr/lib64/R/bin/exec/R ~/core.30387 (gdb) bt 5 #0 0x00007f1dca844ff1 in __strlen_sse2_pminub () from /lib64/libc.so.6 #1 0x00007f1dcb20e8f9 in Rf_mkChar (name=0x0) at envir.c:3725 #2 0x00007f1dcb1dc225 in do_asPOSIXlt (call=<optimized out>, op=<optimized out>, args=<optimized out>, env=<optimized out>) at datetime.c:705 #3 0x00007f1dcb22197f in bcEval (body=b...

Hi Peter, After discovering several bugs in ArgumentPromotion and DeadArgumentElimination where llvm::Functions were replaced with similar functions (with the same name) to transform their type in some way, I started looking at all calls to llvm::Function::takeName to see if there were any other debug info quality bugs in similar callers. One such caller is the DataFlowSanitizer, and I don't

...as keeping the same function as far as debug info >> metadata is concerned) >> >> >>> I compile this with '-O0 -g'. A 'break main'/'run'/'break strlen'/'cont' >>> gives a relevant stack trace: >>> >>> #0 __strlen_sse2_pminub () at >>> ../sysdeps/x86_64/multiarch/strlen-sse2-pminub.S:33 >>> #1 0x00005555555587ff in __dfsw_strlen (s=0x55555556fe17 "foo", >>> s_label=<optimized out>, ret_label=0x7fffffffddee) >>> at llvm/projects/compiler-rt/lib/dfsan/dfsan_custom.c...

...;%H%M") > > 7: format(Sys.time(), format = "%H%M") > > ? ? > > > > I looked into the dumped core with gdb, and found something very strange: > > > > gdb /usr/lib64/R/bin/exec/R ~/core.30387 > > (gdb) bt 5 > > #0 0x00007f1dca844ff1 in __strlen_sse2_pminub () from /lib64/libc.so.6 > > #1 0x00007f1dcb20e8f9 in Rf_mkChar (name=0x0) at envir.c:3725 > > #2 0x00007f1dcb1dc225 in do_asPOSIXlt (call=<optimized out>, > > op=<optimized out>, args=<optimized out>, > > env=<optimized out>) at datetime.c:705...

...e and the wrapper is > created > separately. > > > >>> I compile this with '-O0 -g'. A 'break main'/'run'/'break > strlen'/'cont' > > >>> gives a relevant stack trace: > > >>> > > >>> #0 __strlen_sse2_pminub () at > > >>> ../sysdeps/x86_64/multiarch/strlen-sse2-pminub.S:33 > > >>> #1 0x00005555555587ff in __dfsw_strlen (s=0x55555556fe17 "foo", > > >>> s_label=<optimized out>, ret_label=0x7fffffffddee) > > >>> at llvm/proje...

...> > > > > >>> I compile this with '-O0 -g'. A 'break main'/'run'/'break > > > strlen'/'cont' > > > > >>> gives a relevant stack trace: > > > > >>> > > > > >>> #0 __strlen_sse2_pminub () at > > > > >>> ../sysdeps/x86_64/multiarch/strlen-sse2-pminub.S:33 > > > > >>> #1 0x00005555555587ff in __dfsw_strlen (s=0x55555556fe17 "foo", > > > > >>> s_label=<optimized out>, ret_label=0x7fffffffddee) > >...

...; 6: format(Sys.time(), format = "%H%M") > 7: format(Sys.time(), format = "%H%M") > ? ? > > I looked into the dumped core with gdb, and found something very strange: > > gdb /usr/lib64/R/bin/exec/R ~/core.30387 > (gdb) bt 5 > #0 0x00007f1dca844ff1 in __strlen_sse2_pminub () from /lib64/libc.so.6 > #1 0x00007f1dcb20e8f9 in Rf_mkChar (name=0x0) at envir.c:3725 > #2 0x00007f1dcb1dc225 in do_asPOSIXlt (call=<optimized out>, > op=<optimized out>, args=<optimized out>, > env=<optimized out>) at datetime.c:705 > #3 0x00007f1d...

....6:memcpy@@GLIBC_2.14) redirected to 0x4a24716 (_vgnU_ifunc_wrapper) --3135-- REDIR: 0x53b4d10 (libc.so.6:__memcpy_ssse3_back) redirected to 0x4c2e170 (memcpy@@GLIBC_2.14) --3135-- REDIR: 0x52f32e0 (libc.so.6:strlen) redirected to 0x4a24716 (_vgnU_ifunc_wrapper) --3135-- REDIR: 0x53cf950 (libc.so.6:__strlen_sse2_pminub) redirected to 0x4c2cba0 (strlen) ==3135== Invalid read of size 4 ==3135== at 0x503F6E9: idna_to_ascii_4z (in /usr/lib64/libidn.so.11.6.11) ==3135== by 0x503F977: idna_to_ascii_8z (in /usr/lib64/libidn.so.11.6.11) ==3135== by 0x503F9D9: idna_to_ascii_lz (in /usr/lib64/libidn.so.11.6.11) ==...

WINS nsswitch module -------------------- The WINS nsswitch module has been rewritten to address memory issues and to simplify the code. The module now uses libwbclient to do WINS queries. This means that winbind needs to be running in order to resolve WINS names using the nss_wins module. This does not affect smbd. my problem: old versions >> ping google.com >> PING google.com