Comment 51 for bug 600219

Giuseppe: Some more info that may be helpful: I have reviewed my "/var/log/syslog" files, and have discovered that the faxgetty segfault only occurs when receiving a fax from one particular sender. Of the last 9 faxes received from that sender, 4 came thru OK, and 5 produced segfaults before being completed. When they re-send they fax that produced a segfault, the re-send can segfault on a different page.

I spoke to the sender, and she told me that they have a lot of problems with that machine. It is a Konica/Minolta model 2900.

The only other visible pattern concerns what I presume is the page size on the log entry. Every other sender produces a line in the log file of the form:

<stuff>..RECV FAX (....): from <number>, page 1 in <time>, INF, # line/mm, 2-D MMR, 14400 bit/s

The offending sender has "A4" where the others have "INF". (I am in the USA, where A4 is not a commonly used page size). The offending sender also has "1-D MH" where *most* of the others have "2-D MMR". The 2 other incoming faxes that use "1-D MH" were single page. The logs cover a span of 5 days, during which 41 faxes were received, 6 of which ended prematurely with a segfault. (One segfault occurred while the first page was being received, so the log does not report what number it was originating from).

Regarding the use of gdb: I have not used it before, but I'm willing to give it a shot. The messages you referred to, #15 and #21, are both links to a thread about segfaults occurring when a fax is being sent. So far, I have never had a segfault during a send, even to the machine that causes segfaults when we are receiving. Message #23 appears to have instructions for using gdb with faxgetty, but they are not very clear. Am I to understand that I should run: killall faxgetty; gdb-wrapper.sh faxgetty ttyS0?

Thanks,
Mark