On Sat, 2003-01-25 at 19:25, Mike Vanecek wrote: > ---------- Original Message ----------- > From: Dave Sherman <dsherman@real-time.com> > To: "RedHat 8.0" <psyche-list@redhat.com> > Sent: 25 Jan 2003 07:45:48 -0600 > Subject: Re: Mozilla 1.2.1 > > I had a similar problem, and it turned out that I didn't have Java > > installed. The plugin was there, but the JRE was missing. After I > > installed the JRE and reinstalled the plugin, life was good. > > > > The way I figured it out was to run Mozilla from the command line, and > > watch the error messages that came out just before it crashed. > ------- End of Original Message ------- > > Does anything special need to be set to run Mozilla from the command line > (environmental variables, etc.)? Do you just open a terminal and type mozilla? > > I had some problems with 1.0.1 and 1.2.1 and finally gave up and installed > 1.3a which helped. I would like to have been more conversant in the means of > seeing what was happening. No, I didn't need to do anything special. There is a debugger facility called 'trace', but I have never used it and don't know anything about it. But for normal programs, if you run them from the command line then they will generally print their errors out to a virtual terminal called stderr. And if no stderr has been set, then they go out to the stdout terminal, which is the terminal you are running the program from. Hope this makes sense. I'm not much of a Unix programmer, so I can't really tell you much beyond this. Maybe someone else has some input or correction? Dave
Attachment:
signature.asc
Description: This is a digitally signed message part
