public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "suvarov454 at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug AWT/16708] New: NullPointerException while creating an image with GTK peer Date: Mon, 26 Jul 2004 02:21:00 -0000 [thread overview] Message-ID: <20040726022152.16708.suvarov454@users.sourceforge.net> (raw) When you download the latest CVS HEAD version of MegaMek (http://sourceforge.net/projects/megamek) and follow the instructions in the file, HACKING to build and run MegaMek with the latest GCJ update from the java-gui-branch, you can get a NullPointerException from gnu.java.awt.peer.gtk.GtkImage.GtkImage while creating an image with the following procedure: 1) Run MegaMek. 2) Click the "Map Editor" button in the Splash Screen. 3) Click the "Okay" button in the Set Dimensions dialog of the Map Editor screen. 4) Click on any of the hexes in the Map Editor. The stack trace shows up in the xterm that launched MegaMek or in the log file. -- Summary: NullPointerException while creating an image with GTK peer Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: AWT AssignedTo: fitzsim at redhat dot com ReportedBy: suvarov454 at users dot sourceforge dot net CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16708
next reply other threads:[~2004-07-26 2:21 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-26 2:21 suvarov454 at users dot sourceforge dot net [this message] 2004-07-26 6:31 ` [Bug AWT/16708] " fitzsim at redhat dot com 2005-07-20 19:39 ` fitzsim at redhat dot com 2005-07-20 19:46 ` fitzsim at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20040726022152.16708.suvarov454@users.sourceforge.net \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).