Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 120983 - eclipse crash on long print statements
Summary: eclipse crash on long print statements
Status: RESOLVED DUPLICATE of bug 87299
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.1   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-14 20:03 EST by Florian Vogt CLA
Modified: 2006-01-12 03:11 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Vogt CLA 2005-12-14 20:03:02 EST
The program crashes eclipse:

public class ConsoleBug {

   public static void main(String[] args)
   {
      for (int i=0; i<10000;++i)
      {
	 System.out.print("foo:"+i);
      }
   }
}
Comment 1 Florian Vogt CLA 2005-12-14 20:04:25 EST
eclise crashes on this program 

public class ConsoleBug {

   public static void main(String[] args)
   {
      for (int i=0; i<10000;++i)
      {
	 System.out.print("foo:"+i);
      }
   }
   
   
}
Comment 2 Pascal Rapicault CLA 2005-12-14 21:02:36 EST
Could you detail which type of crash happen?
Do you have something in the log?
Comment 3 Florian Vogt CLA 2005-12-15 13:43:31 EST
Here is the core dump message from the log.

I dont get a stack when I run:
gdb /usr/local/eclipse/eclipse


!SESSION 2005-12-15 10:35:36.56 ------------------------------------------------
eclipse.buildId=I20050627-1435
java.version=1.5.0_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments:  -os linux -ws gtk -arch x86 -consolelog

!ENTRY org.eclipse.core.resources 2 10035 2005-12-15 10:35:39.16
!MESSAGE A workspace crash was detected. The previous session did not exit normally.
The program 'Eclipse' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
  (Details: serial 134037 error_code 14 request_code 1 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Comment 4 Billy Biggs CLA 2006-01-12 03:11:14 EST
What's happening is that the widget is trying to grow past the maximum
size of widgets under X.

*** This bug has been marked as a duplicate of 87299 ***