Hi All,
Thank you all for your input. I'll put a bit more detail in: The RTC means
Return To Command (mode). What I know about faxes is that they start up and
negotiate how they are going to do "it". So the exact protocol, page size, and
transfer speed are agreed. This happens with a bi-directional communication of
1200 or 2400 Baud. Then the actual transfer is done, say in 9600 Baud which was
blistering fast in those days, but at that moment the transfer is one-way only.
So the sender pumps the data and the receiver simply has to chew it. Back then
telephone connections were slightly more troublesome. That is why bad lines are
counted.
At the end of a page the fax goes back to command mode and negotiates further
with the sender. Eventually another page is sent, and after the last page the
whole thing is concluded. Again in command mode.
The switchback at the end of the page is triggered by a particular sequence of
data sent in high speed transfer. Once this RTC code is seen, the "offending
code" is executed.
So, that drives me to the insight that this code is not seldom executed.
At least it is used each fax that is send in a particular mode. And that
is why I have trouble believing it is a compiler problem. And I sure
agree with Giuseppe that the NULL value for this is wrong. But on the
other hand we also get the remark "No such file or directory." And I
cannot see how " if (log) { " can result in this additional "No such
file or directory." I'll do some more digging in the code tonight.
Bye for now,
Simon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/600219
Title:
faxgetty segfault
To manage notifications about this bug go to:
https://bugs.launchpad.net/hylafax/+bug/600219/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
