Giuseppe:
I see your point. My hylafax server is running on a computer dedicated
to that function. I am looking forward to upgrading to 12.04 LTS
specifically because of this bug.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Any new developments with this bug? I have not (yet) installed the
"enhanced logging" packages, as it seemed from Yaztromo's message that
they may not be providing the required information. As before, I am
running the non-optimized packages, and have not yet had another
segfault. If it will help
Yaztromo:
I looks as though nobody has seen any segfaults with the completely un-
optimized packages? I am coming up on a week of running un-optimized
packages without any segfaults, though it took 8 days to catch one when
I was running the "-O" packages. I will have to run unoptimized right
up
Perhaps it is not so easy
gdb seems to exit as soon as a fax is received, even when it does not
cause a segfault. Here is the log after it exits:
toor@isabel:~$ cat /tmp/gdb-4945.log
[New process 4951]
[New process 5045]
Program exited normally.
No stack.
/tmp/gdb-4945.batch:12: Error in
I have received a few more faxes with gdb running, but no segfaults so
far.
As before, gdb exits after each fax is received, and must be manually
re-started. The log file for a normally received fax reads:
root@isabel:/tmp# cat gdb-9245.log
[New process 9251]
[New process 9304]
Program exited
Late breaking news:
I just had a series of segfaults, which has generated 2 ".core" files,
each 878000 bytes long, each with a log file about 4500 bytes long.
Here is one of the log files:
root@isabel:/tmp# cat gdb-9574.log
[New process 9580]
Program received signal SIGSEGV, Segmentation fault
I installed the new packages yesterday. So far, no segfaults. Will
keep watching and waiting
--
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 notificati
I have reached one week since installing the "-O" packages. 77 faxes
have been received during that time, with no segfaults. The OTHER
problem I was having (the computer occasionally freezing until the mouse
is moved) also seems to be fixed. I hope everything continues to work
when I install Ubu
Simon:
I'm not a compiler expert, but it seems to me that "the offending code"
being executed is only a problem when some other process has previously
clobbered the "this" pointer. The offending code itself is probably
fine, but somewhere, perhaps in some data buffer management process
elsewhere,
I was just browsing the source code for ModemServer.c++, and I notice
that ModemServer::vtraceStatus is called by ModemServer::traceStatus,
which has, as one of its arguments, a variable length format string. It
makes me wonder if the format string trailing NULL is what's clobbering
the "this" poi
Simon:
Good points. As I said earlier, back when I was having segfaults, these
patterns emerged: 1) segfaults were very common when receiving from one
particular sender, 2) when a segfault occurred from the problem sender,
the sender would automatically try to send the fax again. It would
ofte
yaztromo:
Glad to hear your setup is working. I am now at 8 days of continuous
running without a segfault, using the "-O" compiled packages. I wonder
why the "-O" compiled packages didn't work for you? Hardware
difference? (My fax server uses an AMD Athlon CPU). Anyway, I hope
this is the end
BAD NEWS!!!
After going for 8 days without a problem, I just had 3 segfaults back-
to-back! All occurred before the originating phone number was logged,
so I can't tell if they were all from the same sender. The last fax
received before the segfaults was from the sender that was causing
problems
I am trying to run a hylafax server in my office, and am getting tripped
up by this same bug. My computer is running Desktop Ubuntu 10.04.4 LTS.
I have tried 2 different serial modems with no difference noted. I
compiled hylafax 6.05 from source, but this did not help.
The segfault seems to occu
Giuseppe: I will be happy to set up my system to generate debugging
traces for you. I will also be paying close attention to when the error
occurs. As I said, it seems that one particular sender seems to
generate the error, but that could just be confirmation bias. After
getting a segfault after
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 bei
Giuseppe:
Just to make sure I have this right: When I try to kill faxgetty, it
immediately respawns. There is an entry in "/etc/init/" named
"ttyS0.conf", which contains:
start on stopped rc RUNLEVEL=[2345]
stop on runlevel [!2345]
respawn
exec /usr/local/sbin/faxgetty ttyS0
I will change t
Giuseppe:
Problem: I renamed "/etc/init/ttyS0.conf" to prevent faxgetty from respawning,
then re-booted.
I ran gdb-wrapper.sh faxgetty ttyS0, but no faxgetty or gdb appeared in the
list of processes. The logs in /tmp/gdb-1565.log say exactly this:
/tmp/gdb-1565.batch:6: Error in sourced comma
Giuseppe/Simon:
I was not in my office yesterday, so I haven't yet tried the repaired
"gdb-wrapper.sh" script.
Looking at the log files, there were 2 segfaults: one was from a number
different from the one that has been causing all of the segfaults to
date, and the other occurred on the first pag
Giuseppe:
I don't know if this is a problem or not.
I killed "faxgetty", then executed "gdb-wrapper.sh
/usr/local/sbin/faxgetty -D ttyS0". Faxgetty once again appears in the
process tree, but the log at /tmp/gdb-24080.log reads:
Program exited normally.
No stack.
/tmp/gdb-24080.batch:11: Error
Giuseppe:
> why don't you just make faxgetty start (and restart automatically) via
> /etc/inittab? Infomation about this
> configuration are in /usr/share/doc/hylafax-server/README.Debian.gz
Recent versions of Ubuntu no longer use the "/etc/inittab" system. The
current method is to have a file
I am half way through our "busy day" at the office, using the "-O"
hylafax-*_6.0.5-5_i386.deb packages (same md5sums as listed in message
#84). So far today, we have received over 25 faxes, and no segfaults
since the packages were installed last week. This is a longer time/more
faxes without a se
22 matches
Mail list logo
