https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87702

Uroš Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #10 from Uroš Bizjak <ubizjak at gmail dot com> ---
Same issue for the second test. Something calls __sscanf with misaligned stack:

Breakpoint 1, __sscanf (
    s=0xffffc1a7 "  357383     799    0    0    0     0          0         1   
88505     798    0    0    0     0       0          0\n", format=0x80ae357
"%llu%llu%u%u%u%u%u%u%llu%llu%u%u%u%u%u%u") at sscanf.c:27
27      in sscanf.c
(gdb) disass
Dump of assembler code for function __sscanf:
=> 0xf7e5c100 <+0>:     push   %ebx
   0xf7e5c101 <+1>:     call   0xf7f278a5 <__x86.get_pc_thunk.bx>
   0xf7e5c106 <+6>:     add    $0x16defa,%ebx
   0xf7e5c10c <+12>:    sub    $0x8,%esp
   0xf7e5c10f <+15>:    lea    0x18(%esp),%eax
   0xf7e5c113 <+19>:    sub    $0x4,%esp
   0xf7e5c116 <+22>:    push   %eax
   0xf7e5c117 <+23>:    pushl  0x1c(%esp)
   0xf7e5c11b <+27>:    pushl  0x1c(%esp)
   0xf7e5c11f <+31>:    call   0xf7e619c0 <_IO_vsscanf>
   0xf7e5c124 <+36>:    add    $0x18,%esp
   0xf7e5c127 <+39>:    pop    %ebx
   0xf7e5c128 <+40>:    ret    
End of assembler dump.
(gdb) i r $sp
sp             0xffffc134       0xffffc134
(gdb) up
#1  0x080568b3 in ?? ()
(gdb) i r $sp
sp             0xffffc138       0xffffc138

Please report these issues to busybox, there is nothing wrong with the compiler
or glibc.

BTW: Provided busybox binary was stripped, so the backtrace doesn't show the
caller name, only:

#2  0xf7e5c124 in __sscanf (
    s=0xffffc1a7 "  355021     777    0    0    0     0          0         1   
86884     779    0    0    0     0       0          0\n", format=0x80ae357
"%llu%llu%u%u%u%u%u%u%llu%llu%u%u%u%u%u%u") at sscanf.c:32
#3  0x080568b3 in ?? ()
#4  0x31323035 in ?? ()
#5  0x20202020 in ?? ()
#6  0x37373720 in ?? ()

Anyway, not our bugs.

Reply via email to