Hi, I got the following message: *** glibc detected *** realloc(): invalid next size: 0x08066da0 *** Aborted at the time, I was running top in an xterm in gnome; if I shrink the vertical size with the mouse a bit fast, it crashes with that message. The crash is reproducible, every time crashes. An strace dump follows: read(7, "", 384) = 0 fcntl64(7, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0 alarm(0) = 1 rt_sigaction(SIGALRM, {0x804ae00, [ALRM], SA_RESTART}, NULL, 8) = 0 close(7) = 0 _llseek(4, 0, [0], SEEK_SET) = 0 read(4, "0.92 0.35 0.22 2/168 28490\n", 4095) = 27 _llseek(5, 0, [0], SEEK_SET) = 0 read(5, "cpu 146952 7556 45952 5365484 6"..., 1024) = 704 _llseek(6, 0, [0], SEEK_SET) = 0 read(6, "MemTotal: 776068 kB\nMemFre"..., 4095) = 670 write(1, "\33[H\33[m\17top - 04:50:41 up 15:39, "..., 1157) = 1157 fcntl64(0, F_GETFL) = 0x2 (flags O_RDWR) fcntl64(0, F_SETFL, O_RDWR|O_NONBLOCK) = 0 read(0, 0xbfffe55b, 1) = -1 EAGAIN (Resource temporarily unavailable) ioctl(0, TCFLSH, 0) = 0 fcntl64(0, F_SETFL, O_RDWR) = 0 select(1, [0], NULL, NULL, {3, 0}) = ? ERESTARTNOHAND (To be restarted) --- SIGWINCH (Window changed) @ 0 (0) --- ioctl(1, TIOCGWINSZ, {ws_row=5, ws_col=122, ws_xpixel=752, ws_ypixel=69}) = 0 open("/dev/tty", O_RDWR|O_NONBLOCK|O_NOCTTY) = 7 writev(7, [{"*** glibc detected *** ", 23}, {"realloc(): invalid next size", 28}, {": 0x", 4}, {"0807ef70", 8}, {" ***\n", 5}], 5) = 68 rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0 gettid() = 28483 tgkill(28483, 28483, SIGABRT) = 0 --- SIGABRT (Aborted) @ 0 (0) --- +++ killed by SIGABRT +++ An ltrace of another run says: fflush(0x401975c0) = 0 read(0, "", 1) = -1 tcflush(0, 0, 1, 2, 0xbfffe560) = 0 fcntl(0, 4, 2, 0, 0x0805e0c0) = 0 select(1, 0xbfffe560, 0, 0, 0x0805e0c0 <unfinished ...> --- SIGWINCH (Window changed) --- ioctl(1, 21523, 0xbfffe1d4) = 0 getenv("COLUMNS") = NULL getenv("LINES") = NULL realloc(0x0807e950, 5945 <unfinished ...> --- SIGABRT (Aborted) --- +++ killed by SIGABRT +++ Now, who can I email this to so that the bug can be solved? Is it a problem with realloc in glibc (dangerous!) or "simply" in top? It is not the only program that crashes this way, pinfo or info does it as well. -- Cheers, Carlos Robinson