On Tue, Apr 18, 2006 at 06:47:41AM +0200, Hanno 'Rince' Wagner wrote:
> Lionel Elie Mamane schrieb am 21. December 2005:

>> Hanno? Did you get my previous email? Have you tried the latest
>> firmware? I you still get this segfault with the latest firmware,
>> I'd really like to report this bug upstream.

> Unfortunately, also with the latest firmware I have that problem.

> Interesting enough is the strace for that command:

> [EMAIL PROTECTED](42):~$ strace c2faxsend -d 497112536214 test.pinguin
> (...)
> write(1, "The config file is /var/spool/hy"..., 58The config file is 
> /var/spool/hylafax/etc/config.faxCAPI. ) = 58
> open("/var/spool/hylafax/etc/config.faxCAPI", O_RDONLY) = 3
> fstat(3, {st_mode=S_IFREG|0644, st_size=15615, ...}) = 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
> 0x2a9556c000
> read(3, "#\n# EDIT THIS CONFIGURATION TO R"..., 4096) = 4096
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> +++ killed by SIGSEGV +++
> -----------------------------------------
> Does this help a little bit?

Ah! I think you are being hit by bug #358567. Try removing empty lines
from your config file (or applying this patch:

--- capi4hylafax-01.03.00.99.svn.296.orig/src/standard/FilePars.cpp
+++ capi4hylafax-01.03.00.99.svn.296/src/standard/FilePars.cpp
                 case '\n':
                     do {
                         curLine.CutLen (1);
-                    } while (  (curLine.GetLastChar() == '\r')
-                            || (curLine.GetLastChar() == '\n'));
+                    } while ( curLine.GetLen() &&
+                             (  (curLine.GetLastChar() == '\r')
+                                || (curLine.GetLastChar() == '\n')));
                     dprint ("ParseLine=(%s)\n", curLine.GetPointer());
                     fret = ParseLine (&curLine);
                     switch (fret) {


)

Or you can nag me every two days until I upload a version that fixes
#358567 :-)

-- 
Lionel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to