[Bug string/29327] A SIGSEGV in hardware optimized memset for sse2 __memset_sse2_unaligned_erms()

["goldstein.w.n at gmail dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=29327

--- Comment #12 from Noah Goldstein <goldstein.w.n at gmail dot com> ---
(In reply to Dr. Werner Fink from comment #9)
> (In reply to Noah Goldstein from comment #3)
> > Are there any steps for reproduction?
> 
> I've tried the memusage script of glibc utils to debug memory consumption of
> kodi Matric 19.4, this works like this:
> 
>  export LD_PRELOAD=/lib64/libmemusage.so
>  export MEMUSAGE_OUTPUT=/dev/null
>  export MEMUSAGE_TRACE_MMAP=yes
> 
> but this make gdb a memory huge eating all physical RAM.
> 
> Therefore I tried to set the environment in gdb its self:
> 
>  gdb --args /usr/lib64/kodi/kodi.bin
>  [...]
>  (gdb) set environment LD_PRELOAD /lib64/libmemusage.so
>  (gdb) set environment MEMUSAGE_OUTPUT /dev/null
>  (gdb) set environment MEMUSAGE_TRACE_MMAP yes
>  (gdb) run
>  Starting program: /usr/lib64/kodi/kodi.bin 
> 
>  Program terminated with signal SIGPROF, Profiling timer expired.
>  The program no longer exists.
>  (gdb) br memset
>  Breakpoint 1 at 0x705f80 (2 locations)
>  (gdb) run
>  Starting program: /usr/lib64/kodi/kodi.bin 
> 
>  Breakpoint 1, memset () at
> ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:125
>  125     ENTRY (MEMSET_SYMBOL (__memset, unaligned))
>  (gdb) list
>  120             cmp     %RDX_LP, %RCX_LP
>  121             jb      HIDDEN_JUMPTARGET (__chk_fail)
>  122     END_CHK (MEMSET_CHK_SYMBOL (__memset_chk, unaligned))
>  123     #endif
>  124
>  125     ENTRY (MEMSET_SYMBOL (__memset, unaligned))
>  126             MEMSET_VDUP_TO_VEC0_AND_SET_RETURN (%esi, %rdi)
>  127     # ifdef __ILP32__
>  128             /* Clear the upper 32 bits.  */
>  129             mov     %edx, %edx
> 
>  (gdb) print $rdi
>  $1 = 140737353858200
>  (gdb) print $rdx
>  $2 = 36
>  (gdb) print $esi
>  $3 = 0

I don't see how those values could segfault,

Are you sure `rdi` points to valid memory?

-- 
You are receiving this mail because:
You are on the CC list for the bug.