"top" core-dumps when console window is shrunk

Bug #162992 reported by monstermunch
This bug report is a duplicate of:  Bug #19277: top crash with resize at mininum. Edit Remove
4
Affects Status Importance Assigned to Milestone
procps (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Hi,

Sorry, I'm not sure what package to report this to. In Kubuntu Gutsy, do the following:

* Run konsole or xterm with a regular sized window.
* Run "top".
* Shrink the window as small as it will go (it will work if you just make it short sometimes too).
* "top" will now report that it has core-dumped.

This is the output I get after doing this:

*** glibc detected *** top: malloc(): memory corruption: 0x00000000006127d0 ***
======= Backtrace: =========
/lib/libc.so.6[0x2b5320abf494]
/lib/libc.so.6(__libc_malloc+0x93)[0x2b5320ac0e23]
/lib/libc.so.6(qsort+0xa7)[0x2b5320a80ae7]
top[0x404886]
top[0x405ff5]
top[0x4087b3]
/lib/libc.so.6(__libc_start_main+0xf4)[0x2b5320a6ab44]
top[0x402299]
======= Memory map: ========
00400000-0040d000 r-xp 00000000 08:09 1197138 /usr/bin/top
0060d000-0060e000 rw-p 0000d000 08:09 1197138 /usr/bin/top
0060e000-00653000 rw-p 0060e000 00:00 0 [heap]
2b53203b1000-2b53203ce000 r-xp 00000000 08:09 1509469 /lib/ld-2.6.1.so
2b53203ce000-2b53203d2000 rw-p 2b53203ce000 00:00 0
2b53205cd000-2b53205cf000 rw-p 0001c000 08:09 1509469 /lib/ld-2.6.1.so
2b53205cf000-2b53205dd000 r-xp 00000000 08:09 1212530 /lib/libproc-3.2.7.so
2b53205dd000-2b53207dc000 ---p 0000e000 08:09 1212530 /lib/libproc-3.2.7.so
2b53207dc000-2b53207dd000 rw-p 0000d000 08:09 1212530 /lib/libproc-3.2.7.so
2b53207dd000-2b53207f1000 rw-p 2b53207dd000 00:00 0
2b53207f1000-2b5320840000 r-xp 00000000 08:09 1212494 /lib/libncurses.so.5.6
2b5320840000-2b5320a40000 ---p 0004f000 08:09 1212494 /lib/libncurses.so.5.6
2b5320a40000-2b5320a4d000 rw-p 0004f000 08:09 1212494 /lib/libncurses.so.5.6
2b5320a4d000-2b5320b9f000 r-xp 00000000 08:09 1509472 /lib/libc-2.6.1.so
2b5320b9f000-2b5320d9e000 ---p 00152000 08:09 1509472 /lib/libc-2.6.1.so
2b5320d9e000-2b5320da1000 r--p 00151000 08:09 1509472 /lib/libc-2.6.1.so
2b5320da1000-2b5320da3000 rw-p 00154000 08:09 1509472 /lib/libc-2.6.1.so
2b5320da3000-2b5320da8000 rw-p 2b5320da3000 00:00 0
2b5320da8000-2b5320daa000 r-xp 00000000 08:09 1509475 /lib/libdl-2.6.1.so
2b5320daa000-2b5320faa000 ---p 00002000 08:09 1509475 /lib/libdl-2.6.1.so
2b5320faa000-2b5320fac000 rw-p 00002000 08:09 1509475 /lib/libdl-2.6.1.so
2b5320fac000-2b5320fae000 rw-p 2b5320fac000 00:00 0
2b5320fae000-2b5320fb6000 r-xp 00000000 08:09 1509479 /lib/libnss_compat-2.6.1.so
2b5320fb6000-2b53211b5000 ---p 00008000 08:09 1509479 /lib/libnss_compat-2.6.1.so
2b53211b5000-2b53211b7000 rw-p 00007000 08:09 1509479 /lib/libnss_compat-2.6.1.so
2b53211b7000-2b53211cd000 r-xp 00000000 08:09 1509478 /lib/libnsl-2.6.1.so
2b53211cd000-2b53213cc000 ---p 00016000 08:09 1509478 /lib/libnsl-2.6.1.so
2b53213cc000-2b53213ce000 rw-p 00015000 08:09 1509478 /lib/libnsl-2.6.1.so
2b53213ce000-2b53213d0000 rw-p 2b53213ce000 00:00 0
2b53213d0000-2b53213da000 r-xp 00000000 08:09 1509773 /lib/libnss_nis-2.6.1.so
2b53213da000-2b53215d9000 ---p 0000a000 08:09 1509773 /lib/libnss_nis-2.6.1.so
2b53215d9000-2b53215db000 rw-p 00009000 08:09 1509773 /lib/libnss_nis-2.6.1.so
2b53215db000-2b53215e5000 r-xp 00000000 08:09 1509756 /lib/libnss_files-2.6.1.so
2b53215e5000-2b53217e4000 ---p 0000a000 08:09 1509756 /lib/libnss_files-2.6.1.so
2b53217e4000-2b53217e6000 rw-p 00009000 08:09 1509756 /lib/libnss_files-2.6.1.so
2b53217e6000-2b53217f3000 r-xp 00000000 08:09 1212482 /lib/libgcc_s.so.1
2b53217f3000-2b53219f3000 ---p 0000d000 08:09 1212482 /lib/libgcc_s.so.1
2b53219f3000-2b53219f4000 rw-p 0000d000 08:09 1212482 /lib/libgcc_s.so.1

Revision history for this message
Daniel Hahler (blueyed) wrote :

Confirmed with procps 1:3.2.7-3ubuntu5.

Revision history for this message
Daniel Hahler (blueyed) wrote :

This has already been reported. I'm marking it as duplicate.

Thank you for your report. Please don't hesitate to report any other issues you may find.

Changed in procps:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.