[Bug uprobes/15972] core dump with process probes

[mjw at redhat dot com]

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

--- Comment #3 from Mark Wielaard <mjw at redhat dot com> ---
The same disassamble before for stap starts tracing:

Dump of assembler code for function g_main_context_iterate:
   0x00007f9476e8df90 <+0>:    push   %r15
   0x00007f9476e8df92 <+2>:    push   %r14
   0x00007f9476e8df94 <+4>:    mov    %esi,%r14d
   0x00007f9476e8df97 <+7>:    push   %r13
   0x00007f9476e8df99 <+9>:    push   %r12
   0x00007f9476e8df9b <+11>:    push   %rbp
   0x00007f9476e8df9c <+12>:    push   %rbx
   0x00007f9476e8df9d <+13>:    mov    %rdi,%rbx
   0x00007f9476e8dfa0 <+16>:    sub    $0x28,%rsp
   0x00007f9476e8dfa4 <+20>:    mov    %edx,0xc(%rsp)
   0x00007f9476e8dfa8 <+24>:    callq  0x7f9476ecd270 <g_mutex_unlock>
   0x00007f9476e8dfad <+29>:    mov    %rbx,%rdi
   0x00007f9476e8dfb0 <+32>:    callq  0x7f9476e8d220 <g_main_context_acquire>

So the int3 is placed on:
0x00007f9476e8dfa8 <+24>:    callq  0x7f9476ecd270 <g_mutex_unlock>

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