Processed: Re: Bug#216849: [sparc] Re: Bug#216849: relocation overflow error

2003-10-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 216849 normal Bug#216849: relocation overflow error Severity set to `normal'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

Bug#216849: [sparc] Re: Bug#216849: relocation overflow error

2003-10-23 Thread Matthias Klose
severity 216849 normal thanks critical is defined as: makes unrelated software on the system (or the whole system) break, or causes serious data loss, or introduces a security hole on systems where you install the package. Ben Collins writes: > This is a bug in the code. Too much allo

Bug#216849: [sparc] Re: Bug#216849: relocation overflow error

2003-10-22 Thread Thomas Nemeth
Le 22.10.03, Ben Collins a tapoté : | > I'm not very familiar with compilers internals but (I once made | > a code-generator, that's all) but how can a double negative can | > happen ? | | It is basically this: | | fprintf(asm_file, "\tsave\t%sp, -%d, %sp\n", size_of_stack); | |

Bug#216849: [sparc] Re: Bug#216849: relocation overflow error

2003-10-22 Thread Ben Collins
> | this overflow of stack in assembly: > | > | read_infos: > | .LLFB46: > | .loc 1 197 0 > | !#PROLOGUE# 0 > | save%sp, --2147483544, %sp > | > | Notice the double negative, produces by overflowing the stack pointer, > > I'm not very familiar with compilers internals but (I

Bug#216849: [sparc] Re: Bug#216849: relocation overflow error

2003-10-22 Thread Thomas Nemeth
Le 22.10.03, Ben Collins a tapoté : | This is a bug in the code. Too much allocation on the stack: | | int read_infos (int socket_data, char **infos) { | int nb; | char datas[SSIZE_MAX]; | | /* SSIZE_MAX = 2147483647 */ | | That's 2 gigs of stack allocation...not likely to happen :) I

Bug#216849: [sparc] Re: Bug#216849: relocation overflow error

2003-10-22 Thread Ben Collins
This is a bug in the code. Too much allocation on the stack: int read_infos (int socket_data, char **infos) { int nb; char datas[SSIZE_MAX]; /* SSIZE_MAX = 2147483647 */ That's 2 gigs of stack allocation...not likely to happen :) It produces this overflow of stack in assembly: read

Bug#216849: [sparc] Re: Bug#216849: relocation overflow error

2003-10-22 Thread Ben Collins
> julie[gacc] make > ==> Building gAcc for Linux/sparc... > Making all in libgacc... > make[1]: Entering directory `/home/thomas/devel/gacc/libgacc' > gcc -c -g3 -I/usr/include -O2 -Wall -I. -I.. -DDEBUG_LEVEL=0 comms.c > /tmp/ccieLhss.s: Assembler messages: > /tmp/ccieLhss.s:6180: Error: reloc

Bug#216849: [sparc] Re: Bug#216849: relocation overflow error

2003-10-22 Thread Thomas Nemeth
Le 22.10.03, Matthias Klose a tapoté : | Thomas, please could you recheck with gcc-3.3.2-1 from unstable? julie[gacc] cat /root/apt-200310221207.log Inst gcc-3.3 [1:3.3.2-0pre5] (1:3.3.2-1 Debian:unstable) julie[gacc] gcc -v Reading specs from /usr/lib/gcc-lib/sparc-linux/3.3.2/specs Configured

Bug#216849: [sparc] Re: Bug#216849: relocation overflow error

2003-10-21 Thread Matthias Klose
[CC to Ben] Thomas, please could you recheck with gcc-3.3.2-1 from unstable? Thomas Nemeth writes: > Package: gcc-3.3 > Version: 3.3.2-0pre5 > Severity: critical > > Hi ! > > I upgraded gcc yesterday : > > julie[gacc] cat /root/apt-200310201058.log | grep gcc > Inst libgcc1 [1:3.3.

Bug#216849: relocation overflow error

2003-10-21 Thread Thomas Nemeth
Package: gcc-3.3 Version: 3.3.2-0pre5 Severity: critical Hi ! I upgraded gcc yesterday : julie[gacc] cat /root/apt-200310201058.log | grep gcc Inst libgcc1 [1:3.3.2-0pre4] (1:3.3.2-0pre5 Debian:testing) Inst gcc-3.3-base [1:3.3.2-0pre4] (1:3.3.2-0pre5 Debian:testing) Inst gcc-3.3