8 messages in net.sourceforge.lists.courier-maildrop[maildropl] Re: How to debug a broken...
FromSent OnAttachments
David BorehamDec 9, 2002 12:11 pm 
Sam VarshavchikDec 9, 2002 2:39 pm 
Johannes ErdfeltDec 9, 2002 3:01 pm 
David BorehamDec 9, 2002 3:09 pm 
David BorehamDec 9, 2002 4:28 pm 
David BorehamDec 10, 2002 7:54 pm 
Sam VarshavchikDec 10, 2002 8:40 pm 
David BorehamDec 10, 2002 9:27 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[maildropl] Re: How to debug a broken maildrop configuration ?Actions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Dec 10, 2002 8:40:42 pm
List:net.sourceforge.lists.courier-maildrop

David Boreham writes:

I see quite a few posts in Google referencing the same problem, and some folk saying that it is a compiler bug (that -fomit-frame-pointer should work with C++ exception-generating code).

When building the RPM, the compiler flags come from a system-dependent file (/user/lib/rpm/remark in my case), which explains why I get -fomit-frame-pointer and others don't.

-fomit-frame-pointer is not the default compiler flag on any Red Hat distro I ever worked on (starting with RH 4.2, and up to the current 8.0).