MToolkit was removed from 1.5 series, and certainly isn't in 1.6. You'll have to revert to an older version.
Maarten. On 11/12/07, Anselm R. Garbe <[EMAIL PROTECTED]> wrote: > First of all, please make sure to subscribe to dwm@ in order to > post messages. > > See below for my thoughts. > > On Mon, Nov 12, 2007 at 12:24:29PM +0100, [EMAIL PROTECTED] wrote: > > The attached message has been automatically discarded. > > Date: Mon, 12 Nov 2007 12:24:28 +0100 > > From: NoName <[EMAIL PROTECTED]> > > To: [email protected] > > Subject: Java Problems in 64 bits > > > > Hi everybody! > > > > I'm having some troubles using java with this Windows System. When I > > have to use a java application, I usually add 'export > > AWT_TOOLKIT=MToolkit' first to make it work correctly. It's fine in a > > 32 bits system, but it has some problems in 64. This is what I have: > > > > > export AWT_TOOLKIT=MToolkit > > > java -jar file.jar > > # > > # An unexpected error has been detected by Java Runtime Environment: > > # > > # SIGSEGV (0xb) at pc=0x00002b8e03a9dd65, pid=30184, tid=1076017488 > > # > > # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.6.0_03-b05 mixed mode) > > # Problematic frame: > > # C [libc.so.6+0x2fd65] catgets+0x15 > > # > > # An error report file with more information is saved as hs_err_pid30184.log > > # > > # If you would like to submit a bug report, please visit: > > # http://java.sun.com/webapps/bugreport/crash.jsp > > # > > Aborted > > > > I have also tried "XToolkit" instead of 'MToolkit". > > > > Any solution? Thanks to everyone. > > I highly recommend to report this issue to the Sun bug tracker > if that's the case. Please make sure, that this is not > dwm-related - hence check if the VM segfaults also with Gnome > when using MToolkit - but actually I won't expect different > behavior, if MToolkit is 32bit only... > > Regards, > -- > Anselm R. Garbe >< http://www.suckless.org/ >< GPG key: 0D73F361 > >
