Closed Bug 16216 Opened 25 years ago Closed 25 years ago

Program has error in startup sequence. [KERNEL32.DLL, XPCOM.DLL]

Categories

(SeaMonkey :: General, defect, P3)

x86
Windows 98
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: netdragon, Assigned: don)

Details

I built 10/11's M10 SeaMonkey source code compiled as debug code successfully.
When I ran apprunner, it caused an error. I debugged the file, and stepped back
to the calling function. It was in function void nsFileURL::operator = (const
nsFilePath& inOther), around line 577 or 578 of xpcom/io/nsFileSpec.cpp
original = 0000003bC:/Program Files/Communications/internet/users50/mozProfile

the last output was startpage= www.mozilla.org

The next error of mine tells about setup.

I believe that the string is not formatted correctly.
Setup never worked. Could that be the reason the string isn't formatted
correctly?
[boberb@rpi.edu, although you might receive a response for this build issue,
you're much more likely to receive a useful one --- faster --- by posting on the
appropriate newsgroup, as listed on the Community page. Good luck.]
OS: other → Windows 98
Summary: Program build doesn't run correctly
Target Milestone: M10
I am changing this to reflect the OS and putting in a summary and Milestone
(forgot).
Will do that also. Is writing to the newsgroup like writing a bug report?
It depends.

In a bug report, the goal is to report an unknown product defect in a fashion
optimized to enable programmers to fix easily and quickly. It's not really
intended as a place that one goes to for help.

e.g. what I'm saying here is completely inappropriate for the context of a bug
report.

In a newsgroup, (in my opinion) the goal is normally to have whatever relevant
interactions with other people with a similar interest (e.g. building Mozilla) in
a less formal context.

If you're already building the code, I'd strongly encourage you to check out
irc.mozilla.org. Lots of helpful people are there.
Isn't it a bug if it doesn't run? I already compiled it. It is in the binary
version just as if I had downloaded it that way.
Note: I downloaded the M10 binaries and ran apprunner and the same thing
happened. Either there is a problem with the application, or it is having
problems because I used to have M9 on my computer. I tried installing the
registry file included and it didn't work. Maybe that info needs to be entered
into the registry. I'm not sure.
Summary: Program build doesn't run correctly → Program has error in startup sequence
The strange thing is, if there was a problem in the binaries, wouldn't someone
have noticed it by now? Therefore, I think there is a problem with the M10 build
when M9 is already on the system.
Summary: Program has error in startup sequence → Program has error in startup sequence.
It appears this is happening to other people on different OSes. Has anyone tried
the Win32 version? Did it work for them? Maybe this is a real problem happening
to more people than just myself.



Startup Window for Compiled Debugging Binary From Source Code:

nsNativeComponentLoader: autoregistering C:\PROGRAMMING\MOZILLA\SOURCE\MOZILLA\D
IST\WIN32_D.OBJ\BIN\components
nsNativeComponentLoader: autoregistering succeeded
started appcores
initialized appshell
ProfileName : mozProfile
ProfileDir  : 0000003bC:\PROGRAM FILES\COMMUNICATIONS\INTERNET\Users50\mozProfil
e
Initialized app shell component {4a85a5d0-cddd-11d2-b7f6-00805f05ffa5}, rv=0x000
00000
XPInstall Component created
Initialized app shell component {18c2f989-b09f-11d2-bcde-00805f0e1353}, rv=0x000
00000
plugins at: C:\PROGRAMMING\MOZILLA\SOURCE\MOZILLA\DIST\WIN32_D.OBJ\BIN\plugins
Start reading in bookmarks.html
Finished reading in bookmarks.html  (160000 microseconds)
Note: styleverifytree is disabled
Note: frameverifytree is disabled
Note: verifyreflow is disabled
Setting content window
browser.startup.page = 1
startpage = www.mozilla.org



Startup Version From the M10 Binary:

Setting content window
browser.startup.page = 1
startpage = www.mozilla.org
Summary: Program has error in startup sequence. → Program has error in startup sequence. [KERNEL32.DLL, XPCOM.DLL]
I get this error every time.

My build:

APPRUNNER caused an exception 03H in module KERNEL32.DLL at 0167:bff768a5.
Registers:
EAX=00000000 CS=0167 EIP=bff768a5 EFLGS=00000246
EBX=008dfbb8 SS=016f ESP=008dd94c EBP=008dd950
ECX=00000244 DS=016f ESI=00008bdc FS=44c7
EDX=10081460 ES=016f EDI=008dfb6c GS=0000
Bytes at CS:EIP:
c3 cc cc 55 8b ec 56 57 68 c0 94 fc bf e8 01 d9
Stack dump:
1000ce69 008dd960 1000cf58 10081460 00000244 008dd984 1002c01b 100814b4 100814a0
10081460 00000244 008dd9c0 02575718 02577738 008dd99c 1002c08e

Your build:
APPRUNNER caused an invalid page fault in
module XPCOM.DLL at 0167:60ad1510.
Registers:
EAX=00000000 CS=0167 EIP=60ad1510 EFLGS=00010216
EBX=00bd2e10 SS=016f ESP=0063eeb8 EBP=0063efc0
ECX=000000a1 DS=016f ESI=0063eff0 FS=515f
EDX=81798d80 ES=016f EDI=0063efec GS=0000
Bytes at CS:EIP:
80 38 00 74 08 50 8b ce e8 1e fa ff ff 5e c9 c3
Stack dump:
0063eff0 00000100 0000010c bff7b9b6 817898f4 0000010c 780012b1 0000003f 00000100
0000010c bff7b9b6 0000003f 0063ef84 012d9dc0 bff7b9b6 817898f4

I think the errors in both cases may be related because one of the errors were
in a cpp file in the xpcom directory, while the other error was in module
xpcom.dll.
I saw someone else's bug about (mozregistry.dat) and I found the same string
(0000003bC:/Program Files/Communications/internet/users50/mozProfile) as I had
found in the variable original. I deleted the file. Mozilla worked and
created a new profile. Now the file contains: (directory
C:\PROGRAMMING\MOZILLA\SOURCE\MOZILLA\DIST\Users50\Brian). Shouldn't Mozilla
have edited the file when it found an invalid string instead of exiting?

I'm glad that was solved.
Perhaps people should be warned about this.
Target Milestone: M10
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
there is already a bug on this, and it's noted in the release notes. It was an
unfortunate incident when you upgrade from M9 from M10 (it was noted in the
release notes). Marking fixed since it's now working for you.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.