Re: [Dspam-devel] css* tools segfault

2010-08-31 Thread Stevan Bajić
On Thu, 26 Aug 2010 17:18:40 +0200 Eric Bischoff wrote: > > Le 26 août 2010 à 12:03, Frantisek Hanzlik a écrit : > > > Stevan Bajić wrote: > > ... > >> > >> I will try to make the other css tools to work again but as said before: > >> this will not fix the fundamental issue with 32/64 bit. >

Re: [Dspam-devel] css* tools segfault

2010-08-31 Thread Stevan Bajić
On Mon, 30 Aug 2010 08:53:56 +0200 Frantisek Hanzlik wrote: > Stevan Bajić wrote: > > > Well... since I have different needs for DSPAM I have started some while > > ago a local fork of DSPAM where I implement stuff that I always wanted to > > have into DSPAM. One of them is to use fixed le

Re: [Dspam-devel] css* tools segfault

2010-08-29 Thread Frantisek Hanzlik
Stevan Bajić wrote: ... > Well... since I have different needs for DSPAM I have started some while ago > a local fork of DSPAM where I implement stuff that I always wanted to have > into DSPAM. One of them is to use fixed length types. I have a local working > version that has the exactly same s

Re: [Dspam-devel] css* tools segfault

2010-08-29 Thread Stevan Bajić
On Wed, 25 Aug 2010 13:13:21 +0200 Julien Valroff wrote: > Hi Stevan, > Hello Julien, > Le mercredi 25 août 2010 à 10:20:48 (+0200), Stevan Bajić a écrit : > > The hash driver has one issue and that is that it is not portable between > > 32bit and 64bit. > > So you need to use a 64bit system

Re: [Dspam-devel] css* tools segfault

2010-08-29 Thread Eric Bischoff
Le 26 août 2010 à 12:03, Frantisek Hanzlik a écrit : > Stevan Bajić wrote: > ... >> >> I will try to make the other css tools to work again but as said before: >> this will not fix the fundamental issue with 32/64 bit. >> >> Looking at the current code I am not sure if the fixes will work with

Re: [Dspam-devel] css* tools segfault

2010-08-26 Thread Frantisek Hanzlik
Stevan Bajić wrote: ... > > I will try to make the other css tools to work again but as said before: this > will not fix the fundamental issue with 32/64 bit. > > Looking at the current code I am not sure if the fixes will work with already > broken css files? I mean: I don't know if fixing the h

Re: [Dspam-devel] css* tools segfault

2010-08-25 Thread Eric Bischoff
> Actually, we didn't have the same problem… I was wrong when setting up my > testing environment on an > i386 machine. > > Stevan, I can also test on amd64 if needed, just tell me if you need it. If anyone needs a ssh to 64 bit machines to do the debugging and the testing, I can offer that (to

Re: [Dspam-devel] css* tools segfault

2010-08-25 Thread Eric Bischoff
> The hash driver has one issue and that is that it is not portable between > 32bit and 64bit. OK. But I also get the problem while staying in pure 64 bits. > So you need to use a 64bit system if the css file was created on a 64bit > installation. That's what I am doing. > I quickly did a pa

Re: [Dspam-devel] css* tools segfault

2010-08-25 Thread Julien Valroff
Le mercredi 25 août 2010 à 10:14:34 (+0200), Eric Bischoff a écrit : > >> Suffer from this myself =( > > > > thanks Eugene for poiting out the second bug report. Actually the user I > > am trying to help is the one who has reported the first bug. > > > > I am surprised that these issues have not

Re: [Dspam-devel] css* tools segfault

2010-08-25 Thread Julien Valroff
Hi Stevan, Le mercredi 25 août 2010 à 10:20:48 (+0200), Stevan Bajić a écrit : > The hash driver has one issue and that is that it is not portable between > 32bit and 64bit. > So you need to use a 64bit system if the css file was created on a 64bit > installation. I know understand what happene

Re: [Dspam-devel] css* tools segfault

2010-08-25 Thread Stevan Bajić
On Wed, 25 Aug 2010 09:34:52 +0200 Eric Bischoff wrote: > > Program received signal SIGSEGV, Segmentation fault. > > [Switching to Thread 0xb74338c0 (LWP 2780)] > > csscompress (filename=0xbfa1f91f "/home/julien/eric.css") at > > csscompress.c:150 > > 150 csscompress.c: No such file or directory

Re: [Dspam-devel] css* tools segfault

2010-08-25 Thread Eric Bischoff
>> Suffer from this myself =( > > thanks Eugene for poiting out the second bug report. Actually the user I > am trying to help is the one who has reported the first bug. > > I am surprised that these issues have not been raised by more people... Actually, if you google the Web, you can find quit

Re: [Dspam-devel] css* tools segfault

2010-08-25 Thread Eric Bischoff
> Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0xb74338c0 (LWP 2780)] > csscompress (filename=0xbfa1f91f "/home/julien/eric.css") at csscompress.c:150 > 150 csscompress.c: No such file or directory. > in csscompress.c > (gdb) bt > #0 csscompress (filename=0xb

Re: [Dspam-devel] css* tools segfault

2010-08-24 Thread Julien Valroff
Le mardi 24 août 2010 à 21:04 +0400, Eugene a écrit : > Hi all, > > - Original Message - > From: "Julien Valroff" > To: > Sent: Tuesday, August 24, 2010 5:53 PM > Subject: [Dspam-devel] css* tools segfault > > > > I am trying to get more in

Re: [Dspam-devel] css* tools segfault

2010-08-24 Thread Eugene
Hi all, - Original Message - From: "Julien Valroff" To: Sent: Tuesday, August 24, 2010 5:53 PM Subject: [Dspam-devel] css* tools segfault > I am trying to get more information to report a possible bug with the hash > backend (helping a user of the Debian packages). &

[Dspam-devel] css* tools segfault

2010-08-24 Thread Julien Valroff
Hi, I am trying to get more information to report a possible bug with the hash backend (helping a user of the Debian packages). This user has issues with the css* tools and I am trying to reproduce the problem on a clean test environment (using Debian Lenny i386 while he is using an amd64 syste