Re: "buffer overflow" error

[Giuseppe Scrivano]

Hello,

yes, the same problem happened for the .deb package.  I didn't
investigate further but I solved it using older versions for libraries.
I reported it both on intrepid and on jaunty, but I can't tell you for
sure which version and which library caused it.  The current .deb based
on hardy works well. I use Ubuntu to generate the .deb as gNewSense uses
Ubuntu packages.

Giuseppe


address@hidden writes:

> Hello,
>
> I have compiled icecat 3.0.7-g1, installed it in my home directory and 
> everything works.
> Then I have decided to build the rpm to install it on my system, and here is 
> the bug : 
>  - when I run the binary "icecat-bin" directly, no problem ;
>  - when I use the launch script "icecat", there is a buffer overflow, with 
> the 
> message
>
>>*** buffer overflow detected ***: ./icecat-bin terminated
>>======= Backtrace: =========
>>/lib64/libc.so.6(__fortify_fail+0x37)[0x303f2ff4c7]
>>/lib64/libc.so.6[0x303f2fd370]
>>/lib64/libc.so.6[0x303f2fda2b]
>>./libxul.so(XRE_GetBinaryPath+0x4d)[0x7fe85124f219]
>>./icecat-bin[0x400ec9]
>>/lib64/libc.so.6(__libc_start_main+0xe6)[0x303f21e576]
>>./icecat-bin[0x400d29]
>>======= Memory map: ========
>>00400000-00402000 r-xp 00000000 fd:01 158405                            
>> /usr/lib64/icecat-3.0.7-g1/icecat-bin 00602000-00603000 rw-p 00002000 fd:01
>> 158405                             /usr/lib64/icecat-3.0.7-g1/icecat-bin
>> 303ec00000-303ec20000 r-xp 00000000 fd:00 9052                          
>> /lib64/ld-2.9.so 303ee1f000-303ee20000 r--p 0001f000 fd:00 9052            
>>               /lib64/ld-2.9.so 303ee20000-303ee21000 rw-p 00020000 fd:00
>> 9052                           /lib64/ld-2.9.so 303f200000-303f368000 r-xp
>> 00000000 fd:00 9055                           /lib64/libc-2.9.so
>> 303f368000-303f568000 ---p 00168000 fd:00 9055                          
>> /lib64/libc-2.9.so 303f568000-303f56c000 r--p 00168000 fd:00 9055          
>>                 /lib64/libc-2.9.so 303f56c000-303f56d000 rw-p 0016c000
>> fd:00 9055                           /lib64/libc-2.9.so
>> 303f56d000-303f572000 rw-p 303f56d000 00:00 0
>>303f600000-303f684000 r-xp 00000000 fd:00 9237                          
>> /lib64/libm-2.9.so 303f684000-303f883000 ---p 00084000 fd:00 9237          
>>                 /lib64/libm-2.9.so 303f883000-303f884000 r--p 00083000
>> fd:00 9237                           /lib64/libm-2.9.so
>> 303f884000-303f885000 rw-p 00084000 fd:00 9237                          
>> /lib64/libm-2.9.so 303fa00000-303fa02000 r-xp 00000000 fd:00 9230          
>>                 /lib64/libdl-2.9.so 303fa02000-303fc02000 ---p 00002000
>> fd:00 9230                           /lib64/libdl-2.9.so
>> 303fc02000-303fc03000 r--p 00002000 fd:00 9230                          
>> /lib64/libdl-2.9.so 303fc03000-303fc04000 rw-p 00003000 fd:00 9230         
>>                  /lib64/libdl-2.9.so 303fe00000-303fe17000 r-xp 00000000
>> fd:00 9248                           /lib64/libpthread-2.9.so
>> 303fe17000-3040016000 ---p 00017000 fd:00 9248                          
>> /lib64/libpthread-2.9.so 3040016000-3040017000 r--p 00016000 fd:00 9248    
>>                       /lib64/libpthread-2.9.so 3040017000-3040018000 rw-p
>> 00017000 fd:00 9248                           /lib64/libpthread-2.9.so
>> 3040018000-304001c000 rw-p 3040018000 00:00 0
>>3040200000-3040215000 r-xp 00000000 fd:00 9250                          
>> /lib64/libz.so.1.2.3 3040215000-3040414000 ---p 00015000 fd:00 9250        
>>                   /lib64/libz.so.1.2.3 3040414000-3040415000 rw-p 00014000
>> fd:00 9250                           /lib64/libz.so.1.2.3
>> 3040600000-3040601000 r-xp 00000000 fd:01 158361                        
>> /usr/lib64/libxcb-xlib.so.0.0.0 3040601000-3040800000 ---p 00001000 fd:01
>> 158361                         /usr/lib64/libxcb-xlib.so.0.0.0
>> 3040800000-3040801000 rw-p 00000000 fd:01 158361                        
>> /usr/lib64/libxcb-xlib.so.0.0.0 3040a00000-3040a05000 r-xp 00000000 fd:01
>> 158359                         /usr/lib64/libXdmcp.so.6.0.0
>> 3040a05000-3040c04000 ---p 00005000 fd:01 158359                        
>> /usr/lib64/libXdmcp.so.6.0.0 3040c04000-3040c05000 rw-p 00004000 fd:01
>> 158359                         /usr/lib64/libXdmcp.so.6.0.0
>> 3040e00000-3040e1a000 r-xp 00000000 fd:01 158360                        
>> /usr/lib64/libxcb.so.1.0.0 3040e1a000-304101a000 ---p 0001a000 fd:01 158360
>>                         /usr/lib64/libxcb.so.1.0.0 304101a000-304101b000
>> rw-p 0001a000 fd:01 158360                        
>> /usr/lib64/libxcb.so.1.0.0 3041200000-3041305000 r-xp 00000000 fd:01 158362
>>                         /usr/lib64/libX11.so.6.2.0 3041305000-3041505000
>> ---p 00105000 fd:01 158362                        
>> /usr/lib64/libX11.so.6.2.0 3041505000-304150b000 rw-p 00105000 fd:01 158362
>>                         /usr/lib64/libX11.so.6.2.0 3041600000-3041602000
>> r-xp 00000000 fd:01 158358                         /u./run-icecat.sh: line
>> 131: 12407 Abandon                 "$prog" ${1+"$@"}
>
> I know that a similar bug was fixed for .deb package 
> <http://lists.gnu.org/archive/html/bug-gnuzilla/2009-03/msg00015.html>
>
> Does someone know what is the origin of the problem and how to fix it ?
> Otherwise do you think it is a good idea to run directly the binary "icecat-
> bin" ?
> Thanks a lot !
>
>
>
> --
> http://gnuzilla.gnu.org