jdk1.4.2: plugin & javaws users feedback request

[Panagiotis Astithas]

On Monday 08 December 2003 23:48, Panagiotis Astithas wrote:
> On Mon, Dec 08, 2003 at 05:53:32PM +0200, Panagiotis Astithas wrote:
> > On Monday 08 December 2003 14:32, Alexey Zelkin wrote:
> > > Gentelmen,
> > >
> > > If you are using jdk1.4.2p5 and also use plugin and/or javaws, then
> > > I would ask you send me your feedbacks (positive and/or negative) about
> > > their correctnes and functionality.  I am not using them heavily, so
> > > not able to test them a lot.
> > >
> > > Thank you in advance!
> >
> > I am quite happy with the plugin, but javaws gives me this when I invoke
> > it:
> >
> > edgar% bash /usr/local/jdk1.4.2/jre/javaws/javaws
> > javawsbin in malloc(): error: allocation failed
> > Abort (core dumped)
> >
> > edgar% gdb /usr/local/jdk1.4.2/jre/javaws/javawsbin javawsbin.core
> > GNU gdb 5.2.1 (FreeBSD)
> > Copyright 2002 Free Software Foundation, Inc.
> > GDB is free software, covered by the GNU General Public License, and you
> > are welcome to change it and/or distribute copies of it under certain
> > conditions. Type "show copying" to see the conditions.
> > There is absolutely no warranty for GDB.  Type "show warranty" for
> > details. This GDB was configured as "i386-undermydesk-freebsd"...
> > (no debugging symbols found)...
> > Core was generated by `javawsbin'.
> > Program terminated with signal 6, Aborted.
> > Reading symbols from /usr/X11R6/lib/libX11.so.6...
> > (no debugging symbols found)...done.
> > Loaded symbols for /usr/X11R6/lib/libX11.so.6
> > Reading symbols from /usr/local/lib/libiconv.so.3...
> > (no debugging symbols found)...done.
> > Loaded symbols for /usr/local/lib/libiconv.so.3
> > Reading symbols from /lib/libc.so.5...(no debugging symbols
> > found)...done. Loaded symbols for /lib/libc.so.5
> > Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols
> > found)... done.
> > Loaded symbols for /libexec/ld-elf.so.1
> > #0  0x2829edbf in kill () from /lib/libc.so.5
> > (gdb) bt
> > #0  0x2829edbf in kill () from /lib/libc.so.5
> > #1  0x28293848 in raise () from /lib/libc.so.5
> > #2  0x2830bff2 in abort () from /lib/libc.so.5
> > #3  0x2830a76e in tcflow () from /lib/libc.so.5
> > #4  0x2830b00b in tcflow () from /lib/libc.so.5
> > #5  0x2830b3c6 in malloc () from /lib/libc.so.5
> > #6  0x08051612 in ReadFileToBuffer ()
> > #7  0x0804df88 in parsePropertyFile ()
> > #8  0x0804b16e in LoadCfgFile ()
> > #9  0x0804b116 in LoadConfigurationFile ()
> > #10 0x08049a4a in main ()
> > #11 0x080498a2 in _start ()
> >
> > This is from a bleeding-edge 5.2-CURRENT, but the jdk14 port was built
> > about a month ago. Any clues?
>
> I got a trace, although I can't make anything useful out of it yet.
> It's at http://noc.ntua.gr/~past/ktrace.out

I have made some more digging around and there is definitely a configuration 
file parsing issue. When I don't have the necessary deployment.properties 
file I get malloc() failures. When I create an empty one I get javawsbin 
hanging in waitpid() - or wait4() to be precise. It seems to be trying to 
make a fork with doodoo data. 

In order to dig some more I tried to make -DWITH_DEBUG, but I don't seem to be 
getting any debug symbols in javawsbin. Is this right? Any clues on how I can 
enable the debugging symbols?
-- 
Panagiotis Astithas
Electrical & Computer Engineer, PhD
Network Management Center
National Technical University of Athens, Greece