Closed Bug 3793 Opened 26 years ago Closed 26 years ago

Solaris: SIGSEV while running apprunner built from CVS source

Categories

(Core :: JavaScript Engine, defect, P1)

Sun
Solaris
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: dejong, Assigned: slamm)

Details

I compiled apprunner from the CVS (dated Thu Mar 4 1999), but when I ran it I got a SIGSEV. Here is the stack dump info I got from gdb. I compiled with gcc. Core was generated by `./apprunner'. Program terminated with signal 9, Killed. #0 0xee3a4674 in strlen () (gdb) bt #0 0xee3a4674 in strlen () #1 0xee3da41c in _doprnt () #2 0xee3e3578 in printf () #3 0xeeb1d620 in NS_ScriptErrorReporter (cx=0xea828, message=0x2fcb70 "BrowserHome is not defined", report=0xefffd920) at ../../../../dom/src/base/nsJSEnvironment.cpp:56 #4 0xeea22b14 in js_ReportErrorAgain (cx=0xea828, message=0x2fcb48 "BrowserHome is not defined", reportp=0xefffd920) at ../../../js/src/jscntxt.c:419 #5 0xeea2290c in js_ReportErrorNumberVA (cx=0xea828, flags=0, callback=0xeea22bb0 <js_GetErrorMessage>, userRef=0x0, errorNumber=1, charArgs=1, ap=0xefffda34) at ../../../js/src/jscntxt.c:378 #6 0xeea19f74 in JS_ReportErrorNumber (cx=0xea828, errorCallback=0xeea22bb0 <js_GetErrorMessage>, userRef=0x0, errorNumber=1) at ../../../js/src/jsapi.c:2566 #7 0xeea22b5c in js_ReportIsNotDefined (cx=0xea828, name=0x2fb5d8 "BrowserHome") at ../../../js/src/jscntxt.c:425 #8 0xeea54144 in js_Interpret (cx=0xea828, result=0xefffde14) at ../../../js/src/jsinterp.c:2209 #9 0xeea48be8 in js_Execute (cx=0xea828, chain=0x10b608, script=0x2fb0c8, fun=0x0, down=0x0, debugging=0, result=0xefffde14) at ../../../js/src/jsinterp.c:815 #10 0xeea1974c in JS_EvaluateUCScriptForPrincipals (cx=0xea828, obj=0x10b608, principals=0x0, chars=0x25ff38, length=14, filename=0xef7988f0 "", lineno=0, rval=0xefffde14) at ../../../js/src/jsapi.c:2324 #11 0xeeb1dad4 in nsJSContext::EvaluateString (this=0x103df8, aScript=@0x25ff10, aURL=0xef7988f0 "", aLineNo=0, aRetValue=@0xefffde88, aIsUndefined=0xefffde9c) at ../../../../dom/src/base/nsJSEnvironment.cpp:89 #12 0xef78afcc in nsXULCommand::ExecuteJavaScriptString (this=0x25ff08, aWebShell=0xdab08, aJavaScript=@0x25ff10) at ../../../../xpfe/appshell/src/nsXULCommand.cpp:171 #13 0xef78ad0c in nsXULCommand::DoCommand (this=0x25ff08) at ../../../../xpfe/appshell/src/nsXULCommand.cpp:133 #14 0xef78b080 in nsXULCommand::MenuSelected (this=0x25ff08, aMenuEvent=@0xefffe0e8) at ../../../../xpfe/appshell/src/nsXULCommand.cpp:185 #15 0xef6b7ae0 in nsMenuItem::MenuSelected (this=0x25fde8, aMenuEvent=@0xefffe0e8) at ../../../../widget/src/gtk/nsMenuItem.cpp:327 #16 0xef6b9a98 in menu_item_activate_handler (w=0x228aa0, p=0x25fde8) at ../../../../widget/src/gtk/nsGtkEventHandler.cpp:592 #17 0xee8e2af0 in gtk_marshal_NONE__NONE (object=0x228aa0, func=0xef6b9928 <menu_item_activate_handler(_GtkWidget *, void *)>, func_data=0x25fde8, args=0xefffe320) at gtkmarshal.c:363 #18 0xee88ba70 in gtk_handlers_run (handlers=0x243240, signal=0xefffe280, object=0x228aa0, params=0xefffe320, after=0) at gtksignal.c:1909 #19 0xee88a98c in gtk_signal_real_emit (object=0x228aa0, signal_id=89, params=0xefffe320) at gtksignal.c:1469 #20 0xee887ad0 in gtk_signal_emit (object=0x228aa0, signal_id=89) at gtksignal.c:552 #21 0xee8d4550 in gtk_widget_activate (widget=0x1) at gtkwidget.c:2810 #22 0xee853040 in gtk_menu_shell_activate_item (menu_shell=0x228e20, menu_item=0x228aa0, force_deactivate=1) at gtkmenushell.c:834 #23 0xee851b7c in gtk_menu_shell_button_release (widget=0x228aa0, event=0xdcdc0) at gtkmenushell.c:497 #24 0xee8e2880 in gtk_marshal_BOOL__POINTER (object=0x228e20, func=0xee8518cc <gtk_menu_shell_button_release>, func_data=0x0, args=0xefffe920) at gtkmarshal.c:32 #25 0xee88a9d4 in gtk_signal_real_emit (object=0x228e20, signal_id=21, params=0xefffe920) at gtksignal.c:1484 #26 0xee887ad0 in gtk_signal_emit (object=0x228e20, signal_id=21) at gtksignal.c:552 #27 0xee8d4328 in gtk_widget_event (widget=0x228e20, event=0xdcdc0) at gtkwidget.c:2784 #28 0xee847a88 in gtk_propagate_event (widget=0x228e20, event=0xdcdc0) at gtkmain.c:1295 #29 0xee846934 in gtk_main_do_event (event=0xdcdc0) at gtkmain.c:752 #30 0xee74c50c in gdk_event_dispatch (source_data=0xdcdc0, current_time=0xefffef08, user_data=0x0) at gdkevents.c:2086 #31 0xee7054a4 in g_main_dispatch (current_time=0xefffef08) at gmain.c:647 #32 0xee705cdc in g_main_iterate (block=1116, dispatch=1) at gmain.c:854 #33 0xee705eec in g_main_run (loop=0xd4098) at gmain.c:912 #34 0xee846164 in gtk_main () at gtkmain.c:475 #35 0xef6ae358 in nsAppShell::Run (this=0x95b50) at ../../../../widget/src/gtk/nsAppShell.cpp:152 #36 0xef78b6e0 in nsAppShellService::Run (this=0x95398) at ../../../../xpfe/appshell/src/nsAppShellService.cpp:154 #37 0x1a884 in main (argc=1, argv=0xeffff244) at ../../../xpfe/bootstrap/nsAppRunner.cpp:265
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
Resolved as duplicate of bug #3792. *** This bug has been marked as a duplicate of 3792 ***
Status: RESOLVED → VERIFIED
QA Contact: 3853
Marking Verified as a dup.
Status: VERIFIED → REOPENED
I do not think this bug is a duplicate of 3792. In fact, I have run into this same error even after 3792 was fixed in the CVS. Please check this bug again. I could be wrong, but I do not think it is the same bug as 3792.
Resolution: DUPLICATE → ---
Assignee: don → slamm
Status: REOPENED → NEW
Priority: P3 → P1
Target Milestone: M4
Re-assigned to slamm@netscape.com, set target milestone to M4, and changed priority to P1. Steve, do you have a Solaris build? If not, can you check whether Chris McAfee has some time to look at this?
Status: NEW → ASSIGNED
I have a Solaris build now. I built today with gcc 2.7.2.3 with the native linker. I don't see a crash. dejong, do you have a way to reproduce this bug? I see you selected a menu item, I don't know what you selected.
Summary: got a SIGSEV while running apprunner from the CVS. → Solaris: SIGSEV while running apprunner built from CVS source
Target Milestone: M4 → M5
I doubt this is an M4 stopper. Moving to M5 while waiting for more data.
I would love to try new builds but it seems like the CVS tree is always broken. I am not trying to rip on anyone, but it really important that the CVS at least build. How can anyone ever hope to test things out when mozilla does not build? Also, is this really something that you need to use the menu to reproduce. Why not just call NS_ScriptErrorReporter from a small main function and see if that dumps core?
Whiteboard: need status update
I can not test to see if this bug has been fixed until bug 5823 is fixed. 5823 describes the crash on startup of apprunner I get from the most recent build of apprunner.
Whiteboard: need status update
Cannot track down this bug until crash on startup is fixed (bug #5661).
Target Milestone: M5 → M6
OK, we're gonna have to wait until mcafee actually fixes the Solaris crash on startup problem before we can even start to fix this. Moving to M6 for now ...
I just built the tree today (Mon May 10) on my Solaris box and I did not see the crash. I am not really sure this is fixed as I do not know what menu combo or race condition created it in the first place but at least it seems to work.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago26 years ago
Resolution: --- → WORKSFORME
This works for me too. Marking WORKSFORME.
QA Contact: 2687
Chris -- we cannot verify this, someone in dev or the reporter will need to do that
Status: RESOLVED → VERIFIED
Ok, I am marking this a VERIFIED. I have run CVS builds on Solaris a number of times and I have not seen this error. If I see it again you can be sure you will hear from me. Thanks.
Component: Apprunner → Javascript Engine
Apprunner component being deleted/retired at end of week. Moving all Apprunner bugs past and present to another appropriate component. Browser-General component has been created as the new "catch-all" component.
You need to log in before you can comment on or make changes to this bug.