Re: [RFH] #486212 reportbug-ng segfaults
Thanks for the hint, unfortunately that didn't help. I've rebuild
python-qt3 with CXXFLAGS="-Wall -g -O0" but rng is still segfaulting.
There is also no bugreport in python-qt3 indicating that someone else
has this problem.
Kęstutis Biliūnas wrote:
An, 2008 07 08 15:44 +0200, Bastian Venthur rašė:
since a few feeks reportbug-ng segfaults quite often. Since I haven't
made any changes in this time, I think one of the libs rng depends on is
the problem. Currently it depends on python-soappy and python-qt3. I
think SOAPpy is not the problem, since I played around with it a few
days ago and never got a segfault.
So I think it's python-qt3. The bugreport #486212 has a backtrace, but
I'm not sure how to interpret the output in this case. Can anybody help
me to track down the problem and find out whether it is qt3, python or
I guess the problem is related with gcc , because gcc-4.3 is now the
default compiler. Now we have the similar problem with fonforge package
(#487101). If I build fontforge using gcc-4.2, I can't to reproduce the
bug. Also the problem disappear if I build using gcc-4.3, but without
the optimization (CFLAGS="-Wall -g -O0"). So, I advise you to do so