Closed
Bug 327766
Opened 19 years ago
Closed 14 years ago
termination right after startup. no core. Program received signal ?, Unknown signal. InstallUnixSignalHandlers
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: g.fischer, Unassigned)
Details
(Whiteboard: [closeme 2011-06-30])
User-Agent: Mozilla/5.0 (X11; U; IRIX64 IP27; en-US; rv:1.9a1) Gecko/R-A-C SeaMonkey/1.5a
Build Identifier:
irix 6.5.28/29, mipspro 7.43, current checkouts of seamonkey and firefox.(happens with both)
----
directly after starting it up it's terminated. no core.
little debugging here:
(gdb) r
Starting program: /mnt/3/moz/obj/dist/bin/seamonkey-bin
Program exited with code 01.
(gdb) r
Starting program: /mnt/3/moz/obj/dist/bin/seamonkey-bin
Program exited with code 01.
(gdb) b main
Breakpoint 1 at 0x1000a494: file nsAppRunner.cpp, line 1566.
(gdb) r
Starting program: /mnt/3/moz/obj/dist/bin/seamonkey-bin
Program received signal ?, Unknown signal.
main () at nsAppRunner.cpp:1566
1566 InstallUnixSignalHandlers(argv[0]);
(gdb) bt
#0 main () at nsAppRunner.cpp:1566
(gdb) c
Continuing.
warning: Signal ? does not exist on this system.
Program exited with code 01.
any hints are welcome.
must have happened between 23.jan.06 and now because i made a running build on 23/01.
Reproducible: Always
Steps to Reproduce:
1.start the app
2.
3.
Actual Results:
no window, immediate termination. no core etc.
Expected Results:
run
i tried several users even new ones to exclude some userprofile issues.
| Reporter | ||
Comment 1•19 years ago
|
||
same using a firefox checkout from today:
Use 'stop at 1' and 'run' commands first to remove overlaps.
Overlapping regions: 0x400000 to 0x556198 and 0x400000 to 0x405165
Executable /mnt/3/moz/obj/dist/bin/./firefox-bin
(dbx) stop at 1
Process 0: [3] stop at "/mnt/3/moz/mozilla/browser/app/nsBrowserApp.cpp":60
Process 0: [4] stop at "/mnt/3/moz/mozilla/browser/app/nsBrowserApp.cpp":60
(dbx) r
Process 114116 (firefox-bin) started
[3] Process 114116 Thread 0x10000 (firefox-bin) stopped at [::main:60 ,0x10002940]
60 {
(dbx) c
[4] Process 114116 Thread 0x10000 (firefox-bin) stopped at [::main:60 ,0x1000295c]
60 {
(dbx) c
Process 114116 (firefox-bin) terminated
Comment 2•14 years ago
|
||
Is this still happening with a current version?
Whiteboard: [closeme 2011-06-30]
Updated•14 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Updated•7 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•