Crash when recording clock_gettime

Robert O'Callahan robert at ocallahan.org
Mon Aug 28 21:36:21 UTC 2017


On Tue, Aug 29, 2017 at 8:14 AM, Benjamin King <benjaminking at web.de> wrote:

> clock_gettime from my libc disassembles to this:
> ----
> 0000000000115810 <__clock_gettime@@GLIBC_PRIVATE>:
>  115810:        55                      push   %rbp
>  115811:        53                      push   %rbx
>  115812:        48 89 f5                mov    %rsi,%rbp
>  115815:        89 fb                   mov    %edi,%ebx
>  115817:        48 83 ec 08             sub    $0x8,%rsp
>  11581b:        48 8b 05 c6 3a 2b 00    mov    0x2b3ac6(%rip),%rax
> # 3c92e8 <_dl_open_hook@@GLIBC_PRIVATE+0x8>
>  115822:        48 c1 c8 11             ror    $0x11,%rax
>  115826:        64 48 33 04 25 30 00    xor    %fs:0x30,%rax
>  11582d:        00 00  11582f:  48 85 c0                test   %rax,%rax
>  115832:        74 2c                   je     115860 <__clock_gettime@
> @GLIBC_PRIVATE+0x50>
>  115834:        ff d0                   callq  *%rax
>  ...
> ----
>
> Both commit e7b00db and the previous one are going through this, but the
> call
> to *%rax sends rr commit e7b00db to a bunch of instructions that are not in
> the disassembly of my libc. I also fail to understand what they are
> supposed
> to do and they crash, eventually.
>

Can you paste the disassembly of those instructions at *%rax in the failing
case? Also, if you look up /proc/<pid>/maps for the process you should be
able to see the mapping they belong to.

Thanks,
Rob
-- 
lbir ye,ea yer.tnietoehr  rdn rdsme,anea lurpr  edna e hnysnenh hhe uresyf
toD
selthor  stor  edna  siewaoeodm  or v sstvr  esBa  kbvted,t
rdsme,aoreseoouoto
o l euetiuruewFa  kbn e hnystoivateweh uresyf tulsa rehr  rdm  or rnea
lurpr
.a war hsrer holsa rodvted,t  nenh hneireseoouot.tniesiewaoeivatewt sstvr
esn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/rr-dev/attachments/20170829/e3b44663/attachment.html>


More information about the rr-dev mailing list