public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "mckinlay at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug AWT/17254] [java-gui-branch] Hang when resizing AWT window on Alpha
Date: Wed, 01 Sep 2004 15:11:00 -0000	[thread overview]
Message-ID: <20040901151151.12266.qmail@sourceware.org> (raw)
In-Reply-To: <20040831212751.17254.falk@debian.org>


------- Additional Comments From mckinlay at redhat dot com  2004-09-01 15:11 -------
So, it does hang under GDB, but doesn't throw the exception?

The stack trace you gave is that of the finalizer thread, which probably isn't
interesting here. Try using the "info threads" and "thread n" commands to switch
to the other threads and get traces of those.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17254


  parent reply	other threads:[~2004-09-01 15:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31 21:28 [Bug AWT/17254] New: " falk at debian dot org
2004-08-31 21:30 ` [Bug AWT/17254] " falk at debian dot org
2004-08-31 21:32 ` falk at debian dot org
2004-08-31 21:51 ` fitzsim at redhat dot com
2004-08-31 22:18 ` falk at debian dot org
2004-08-31 22:22 ` mckinlay at redhat dot com
2004-08-31 22:46 ` falk at debian dot org
2004-08-31 23:08 ` mckinlay at redhat dot com
2004-09-01  6:51 ` falk at debian dot org
2004-09-01 15:11 ` mckinlay at redhat dot com [this message]
2004-09-01 15:36 ` falk at debian dot org
2004-09-02  7:42 ` graydon at redhat dot com
2004-09-02 15:00 ` fitzsim at redhat dot com
2005-05-30 15:46 ` fitzsim at redhat dot com
2005-08-21 15:36 ` [Bug awt/17254] " fitzsim at redhat dot com
     [not found] <bug-17254-2744@http.gcc.gnu.org/bugzilla/>
2005-10-16  1:48 ` pinskia at gcc dot gnu dot org

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=20040901151151.12266.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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: link
Be 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).