GNOME Bugzilla – Bug 421851
buffer overflow
Last modified: 2007-07-02 12:03:36 UTC
Please describe the problem: At starting the program a buffer overflow happens Steps to reproduce: 1. 2. 3. Actual results: Starting with the command in the shell: beast then the Program crash. see report. Expected results: Does this happen every time? yes Other information: *** buffer overflow detected ***: beast terminated ======= Backtrace: ========= /lib64/libc.so.6(__chk_fail+0x2f)[0x2afce2d9ad4f] /lib64/libc.so.6[0x2afce2d99df3] beast[0x400e58] beast[0x400c3b] /lib64/libc.so.6(__libc_start_main+0xf4)[0x2afce2ce5ae4] beast[0x4009b9] ======= Memory map: ======== 00400000-00402000 r-xp 00000000 08:06 5458462 /usr/bin/beast 00601000-00603000 rw-p 00001000 08:06 5458462 /usr/bin/beast 00603000-00624000 rw-p 00603000 00:00 0 [heap] 2afce2aaa000-2afce2ac6000 r-xp 00000000 08:06 2162690 /lib64/ld-2.5.so 2afce2ac6000-2afce2ac7000 rw-p 2afce2ac6000 00:00 0 2afce2af7000-2afce2af8000 rw-p 2afce2af7000 00:00 0 2afce2cc6000-2afce2cc8000 rw-p 0001c000 08:06 2162690 /lib64/ld-2.5.so 2afce2cc8000-2afce2e01000 r-xp 00000000 08:06 2162697 /lib64/libc-2.5.so 2afce2e01000-2afce3000000 ---p 00139000 08:06 2162697 /lib64/libc-2.5.so 2afce3000000-2afce3003000 r--p 00138000 08:06 2162697 /lib64/libc-2.5.so 2afce3003000-2afce3005000 rw-p 0013b000 08:06 2162697 /lib64/libc-2.5.so 2afce3005000-2afce300b000 rw-p 2afce3005000 00:00 0 2afce300b000-2afce3018000 r-xp 00000000 08:06 2162741 /lib64/libgcc_s.so.1 2afce3018000-2afce3217000 ---p 0000d000 08:06 2162741 /lib64/libgcc_s.so.1 2afce3217000-2afce3219000 rw-p 0000c000 08:06 2162741 /lib64/libgcc_s.so.1 7fffc7fe8000-7fffc8000000 rw-p 7fffc7fe8000 00:00 0 [stack] ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0 [vdso] Abgebrochen
hi. unfortunately the information you give isn't suitable to reproduce the error you're encountering. also the backtrace doesn't show why the libc function __chk_fail() was triggered, please provide system details (linux version, libc version etc.) and a backtrace with debugging symbols next time (this may require installing system libraries with debugging symbols).
*** This bug has been marked as a duplicate of 452604 ***