aboutsummaryrefslogtreecommitdiffstats
path: root/fetchmail-FAQ.html
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>1997-06-05 15:04:53 +0000
committerEric S. Raymond <esr@thyrsus.com>1997-06-05 15:04:53 +0000
commit604bf51c4d000e2dd2eed65c40ef6219811d9fd9 (patch)
treeecdd668cc4551813cca76385b7d55a750a9d82f4 /fetchmail-FAQ.html
parent77cc256ed6094b52f0d552e8744b9722d28ff396 (diff)
downloadfetchmail-604bf51c4d000e2dd2eed65c40ef6219811d9fd9.tar.gz
fetchmail-604bf51c4d000e2dd2eed65c40ef6219811d9fd9.tar.bz2
fetchmail-604bf51c4d000e2dd2eed65c40ef6219811d9fd9.zip
Scott reports the R5 bug in 3.9.6.
svn path=/trunk/; revision=1063
Diffstat (limited to 'fetchmail-FAQ.html')
-rw-r--r--fetchmail-FAQ.html9
1 files changed, 5 insertions, 4 deletions
diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html
index 2ecaf294..3919de37 100644
--- a/fetchmail-FAQ.html
+++ b/fetchmail-FAQ.html
@@ -781,10 +781,11 @@ by fetchmail, either).<p>
<hr>
<h2><a name="R5">R5. Fetchmail dumps core when I use a .netrc file but works otherwise.</a></h2>
-We have a report that under Solaris 2.5, if fetchmail is compiled with -O2
-or -O3, it segfaults on startup when reading a .netrc.<p>
+We have a report that under Solaris 2.5 using gcc-2.7.2, if fetchmail
+is compiled with -O or -O2, it segfaults on startup when reading a
+.netrc.<p>
-You can work around this by dropping back to -O.<p>
+You can work around this by disabling optimization.<p>
There may be an actual bug here that the optimizer exposes; the stack
trace says the segfault is in free() and has all the earmarks of a heap-
@@ -993,7 +994,7 @@ without hacking potentially fragile startup scripts. To get around
it, just touch(1) the logfile before you run fetchmail (this will have
no effect on the contents of the logfile if it already exists).<P>
-$Id: fetchmail-FAQ.html,v 1.24 1997/06/04 12:56:07 esr Exp $<p>
+$Id: fetchmail-FAQ.html,v 1.25 1997/06/05 15:04:53 esr Exp $<p>
<HR>
<ADDRESS>Eric S. Raymond <A HREF="mailto:esr@thyrsus.com">&lt;esr@snark.thyrsus.com&gt;</A></ADDRESS>