I've determined that this only happens when TERM=xterm-color. TERM
values that work without producing a segfault are xterm, ansi, vt100,
and vt220.
** Summary changed:
- segfault on amd64 as non-root user
+ top segfault when TERM=xterm-color
** Description changed:
- top segfaults right away when run as a non-root user. I rebuilt it with
+ top segfaults right away when run as a non-root user. It does not
+ segfault when run as root with the same TERM value. I rebuilt it with
debugging symbols:
rogram received signal SIGSEGV, Segmentation fault.
0x00002aaaaaeb0a40 in strcpy () from /lib/libc.so.6
(gdb) bt
#0 0x00002aaaaaeb0a40 in strcpy () from /lib/libc.so.6
#1 0x0000000000402d85 in capsmk (q=0x50ee18) at top.c:533
#2 0x0000000000404505 in windows_stage2 () at top.c:2463
#3 0x0000000000407f4d in main (dont_care_argc=<value optimized out>,
argv=0x7fffff874678) at top.c:3322
(gdb) f 1
#1 0x0000000000402d85 in capsmk (q=0x50ee18) at top.c:533
533 strcpy(q->capclr_sum, tparm(set_a_foreground, q->rc.summclr));
(gdb) print q
$1 = (WIN_t *) 0x50ee18
(gdb) print q->capclr_sum
$2 = '\0' <repeats 63 times>
(gdb) print q->rc
$4 = {sortindx = 0, winflags = 63801, maxtasks = 0, summclr = 6, msgsclr = 6,
headclr = 7, taskclr = 6, winname = "Job",
fieldscur = "ABcefgjlrstuvyzMKNHIWOPQDX\000\000\000\000\000"}
--
top segfault when TERM=xterm-color
https://launchpad.net/bugs/58405
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
