[Bug 11751] New: chrt Segmentation fault

bugzilla at busybox.net bugzilla at busybox.net
Thu Apr 4 15:48:53 UTC 2019


https://bugs.busybox.net/show_bug.cgi?id=11751

            Bug ID: 11751
           Summary: chrt Segmentation fault
           Product: Busybox
           Version: 1.29.x
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at busybox.net
          Reporter: yangtze31 at gmail.com
                CC: busybox-cvs at busybox.net
  Target Milestone: ---

chrt woks with Buildroot 2018.02.x, now Segmentation fault with Buildroot
2019.02.1

I don't know how to debug.

pid 198 is one of the four threads of mpd.
chrt works with others pids, but with this one:
# chrt -p 198
Segmentation fault

# gdb --args chrt -p 198
GNU gdb (GDB) 8.1.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "aarch64-buildroot-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from chrt...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/chrt -p 198

Program received signal SIGSEGV, Segmentation fault.
0x0000ffffb24f6510 in strlen () from /lib64/libc.so.6
(gdb) bt
#0  0x0000ffffb24f6510 in strlen () from /lib64/libc.so.6
#1  0x0000ffffb24c3e80 in vfprintf () from /lib64/libc.so.6
#2  0x0000ffffb24c99fc in printf () from /lib64/libc.so.6
#3  0x000000000042fd94 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

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


More information about the busybox-cvs mailing list