Hylafax Developers Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[hylafax-devel] Re: Bug not fixed
Found some time to look at this.
> Could you insert a couple of lines before, perhaps something like:
>
> fxStr s = "strlen(buf) = " + strlen(buf);
> (void) Sys::write(fd, s, s.length());
OK
> s = "fmt = " + fmt;
> (void) Sys::write(fd, s, s.length());
... this fails to compile, a type mismatch, I think.
Where does the output from these print statements go?
Iain
... old message follows ....
>Hi guys,
>
>I installed the latest CVS version of hylafax this evening on my Mac - now
>running Yellow Dog CS 1.2 with a 2.2.16 kernel. Everything compiled fine
>but the problem with faxgetty crashing remains. It is necessary to remove
>this line:
>
> vsprintf(buf+strlen(buf), (const char*) fmt, ap);
>
>... which is the third line from the bottom of FaxMachineLog.c++ (as I've
>found before) to make faxgetty work.
I haven't seen this on any other platform - the only possible thing i think
it could be doing is overflowing the buffer(which is quite large 16k) or
perhaps there is something strange about the fmt string.
Could you insert a couple of lines before, perhaps something like:
fxStr s = "strlen(buf) = " + strlen(buf);
(void) Sys::write(fd, s, s.length());
s = "fmt = " + fmt;
(void) Sys::write(fd, s, s.length());
vsprintf(buf+strlen(buf), (const char*) fmt, ap);
(void) Sys::write(fd, buf, strlen(buf));
...
just to see what is going on.
PS or perhaps the ap variable is all messed up.
- Robert
____________________ HylaFAX(tm) Developers Mailing List ____________________
To unsub: mail -s unsubscribe hylafax-devel-request@hylafax.org < /dev/null