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, the address of the current "ModemServer" instance is getting
replaced by "0". Once that happens, any attempt to access a member of
ModemServer will cause a segfault. The problem isn't at line 950 (if
(log) { ), it's somewhere before that. Line 950 is just the first time
the program has a chance to fail because of the error.
Mark
--
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
