Bug 111662 - mozilla crashes on startup when built with gcc 3.3
Summary: mozilla crashes on startup when built with gcc 3.3
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: mozilla
Version: 1
Hardware: powerpc
OS: Linux
medium
high
Target Milestone: ---
Assignee: Christopher Blizzard
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-12-08 10:04 UTC by Alex Kiernan
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-01-20 19:52:19 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Patch to spec file to apply nsCOMPtr patch (620 bytes, patch)
2003-12-08 10:05 UTC, Alex Kiernan 		no flags Details | Diff
Existing bugzilla.mozilla.org patch modified for 1.4.1-18 (1.05 KB, patch)
2003-12-08 10:06 UTC, Alex Kiernan 		no flags Details | Diff
View All

Description Alex Kiernan 2003-12-08 10:04:08 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.4.1)
Gecko/20031203 Epiphany/1.0.4

Description of problem:
Mozilla 1.4.1 is miscompiled by gcc 3.3 due to an aliasing problem in
the codebase (http://bugzilla.mozilla.org/show_bug.cgi?id=212082).



Version-Release number of selected component (if applicable):
mozilla-1.4.1-18

How reproducible:
Always

Steps to Reproduce:
Run mozilla on a ppc box
    

Additional info:
Comment 1 Alex Kiernan 2003-12-08 10:05:06 UTC 
Created attachment 96393 [details]
Patch to spec file to apply nsCOMPtr patch
Comment 2 Alex Kiernan 2003-12-08 10:06:39 UTC 
Created attachment 96394 [details]
Existing bugzilla.mozilla.org patch modified for 1.4.1-18
Comment 3 Paul Nasrat 2003-12-17 14:12:12 UTC 
These patches are fix correctly the bug worked around described here

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=109691
Comment 4 Christopher Blizzard 2004-01-20 19:52:19 UTC 
Mozilla 1.6 is now in the rawhide tree and that includes these fixes.
 Marking RAWHIDE.
Note You need to log in before you can comment on or make changes to this bug.