Closed Bug 256382 Opened 20 years ago Closed 19 years ago

Darwin 7 builds crash on startup

Categories

(Firefox Build System :: General, defect)

1.7 Branch
PowerPC
Other
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: yves, Unassigned)

Details

(Keywords: crash)

Attachments

(4 files)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; fr-ca) AppleWebKit/125.4 (KHTML, like Gecko) Safari/125.9 Build Identifier: http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.6/src/ Mozilla built on Darwin 7 crashes at startup, even before building a stack (gdb core: no stack). Mozilla built on MacOSX 10.3 will not run on Darwin OS because it links to the CoreServices framework which is proprietary and MacOSX only. Reproducible: Always Steps to Reproduce: 1. 2. 3.
PS : I also tried mozilla-1.7.2 on OpenDarwin-7.2.1 and it crashed at startup too. I also tried various configurations.
MacOSX builds require CoreServices and I don't believe that's going to change for the functionality required. When building on Darwin 7, what options are you using? Please attach the configure output of the build.
Keywords: crash
OS: MacOS X → other
Summary: Mozilla won't run on Darwin OS because it links to CoreServices Framework → Darwin 7 builds crash on startup
./configure --enable-default-toolkit=gtk2 --mandir=${prefix}/share/man \ --enable-optimize --enable-crypto --enable-calendar
I meant the actual ouptut of the configure command. config.log is a bit harder to follow. Does a debug build (--disable-optimize --enable-debug) exhibit the same crash w/o a stack behavior?
Attached file configure output
Attached file what I tried in gdb
Note that I am not very good with gdb (if you have not guessed yet)
The configure output and gdb output are both with --disable-optimize and --enable-debug. I also have the whole build output if you want (5 Mb)
I see the gdb attempt is after doing a 'make install'. You'll need to run gdb with the proper library paths set for that. Just try `./mozilla -g` . Also, have you tried running mozilla from dist/ ? cd dist/bin && ./mozilla
./mozilla -g ! thanks for that one The program gets through a bunch of _dyld_* functions and then seems to crash in crt.c which is referenced in /usr/src/APPLE... (probably crt2.o) So I tried to build it with FSF gcc-3.4.0 but the build does not get passed nsIConsoleListener.idl ../../dist/bin/xpidl -m header -w -I. -I../../dist/idl -o _xpidlgen/nsIConsoleListener nsIConsoleListener.idl Assertion failed: state->tree, file xpidl_idl.c, line 60
note that for FSF gcc, I had to quickly remove -fPascal-strings and -Wmost since thos flags were not recognized. Maybe it is related with the build failure.
Can you attach the complete stack trace from the './mozilla -g' debug run?
Attached file gdb.log with backtrace
bryner, any ideas what's going on here with gdb?
Could someone point me from which version did mozilla begin to include CoreServices ? I know 1.0.0 does not show this problem.
Mozilla 1.0.0 doesn't build on Darwin/OSX, either, iirc. We didn't officially start supporting Darwin/OSX until Mozilla 1.3 or so and afaik, we've always required CoreServices. We didn't start supporting non-OSX darin builds until some time after that (moz1.5?). There is a related bug (bug #249028) to make non-OSX darwin builds not require CoreServices as they currently do.
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: SeaMonkey → Core
Version: Trunk → 1.7 Branch
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: