Hi Mark, hi Guiseppe,
Yes, sure, we are all on one line here. And Mark, in my mind there is no
doubt that "if (log) {" is not causing the problem. And yes, the this
pointer is damaged some other way. BUT if this would be due to a
compiler issue I have trouble to accept that this happens only once
every 50 faxes. So, what I try to say is, could it not be a combination
of programming error (buffer overrun), malicious input (damaged/ill
formatted input data) and the optimalisation used by the compiler
(different -O option produces different code that may or may not fail).
So, I think that by more analysis we may learn more. We may be able to corner
the problem further it we could more exactly describe when this happens. Is it
for example only in multi-page faxes? Or is it only after the last page?
That was also why I noted that this code is running often. Every fax received
does at least once do a RTC. So, I tried to ask, what is the extraordinary (or
additional) circumstance on top of doing this RTC logging that causes the
failure? Sorry for not having been clearer before.
At the same time I still do not understand where the "no such file or
directory". What is that trying to tell?
Regards, 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
