Bug 358588 - Fatal Error 177:17
Summary: Fatal Error 177:17
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.2   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2011-09-22 09:34 EDT by Dov Nimratz CLA
Modified: 2011-09-29 07:05 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dov Nimratz CLA 2011-09-22 09:34:39 EDT 
Build Identifier: epp.package.cpp

9/22/11 4:14:15 PM	[0x0-0x93093].org.eclipse.eclipse[2693]	[Fatal Error] :177:17: An invalid XML character (Unicode: 0x{2}) was found in the value of attribute "{1}" and element is "0".

Reproducible: Always

Steps to Reproduce:
1. Print
2.
3.
Comment 1 Remy Suen CLA 2011-09-22 11:32:31 EDT 
How do I reproduce this problem? Try to print an XML document?
Comment 2 Dani Megert CLA 2011-09-23 01:55:10 EDT 
>1. Print
From which editor do you print?
Comment 3 Dov Nimratz CLA 2011-09-23 03:10:08 EDT 
I print from build in editor
Comment 4 Dani Megert CLA 2011-09-23 03:47:13 EDT 
(In reply to comment #3)
> I print from build in editor

Use context menu  > Open With to see which editor is used and report it here.
Comment 5 Dov Nimratz CLA 2011-09-23 04:08:33 EDT 
Xcode
Comment 6 Dani Megert CLA 2011-09-23 04:13:14 EDT 
(In reply to comment #5)
> Xcode

This is not part of the Eclipse SDK. You need to report the bug to the Xcode editor provider.
Comment 7 Dov Nimratz CLA 2011-09-23 04:51:09 EDT 
Grate bag fix!
Unfortunately Eclipse crashed from Eclipse editor wit system bug trace shows Eclipse point of error.
Comment 8 Remy Suen CLA 2011-09-23 06:32:33 EDT 
(In reply to comment #7)
> Unfortunately Eclipse crashed from Eclipse editor

But I thought you were using Xcode?
Comment 9 Dov Nimratz CLA 2011-09-23 08:07:49 EDT 
I will repeat from very beginning:
During printing in Eclipse IDE, Eclipse stuck without any possibility even to close it.
I kill it from console as a process.
With system log I found error message, that send with report.
During the day Eclipse stucks again few time.
Comment 10 Remy Suen CLA 2011-09-23 08:12:27 EDT 
(In reply to comment #9)
> I will repeat from very beginning:
> During printing in Eclipse IDE, Eclipse stuck without any possibility even to
> close it.

When Eclipse hangs, please get a thread dump and then attach it to this bug report.

Not sure why Xcode was mentioned in comment 5, I guess there was a communication problem.
Comment 11 Remy Suen CLA 2011-09-23 08:12:48 EDT 
(In reply to comment #10)
> When Eclipse hangs, please get a thread dump and then attach it to this bug
> report.

Here are some ways in which you can get a thread dump.
http://wiki.eclipse.org/index.php/How_to_report_a_deadlock
Comment 12 Dov Nimratz CLA 2011-09-26 10:57:29 EDT 
I had run eclipse with heap dump option and it was crashed.
Where I can find dump file to send you?
Comment 13 Dov Nimratz CLA 2011-09-29 05:55:13 EDT 
Following lines after crash:


Dov-Nimratzs-MacBook-Pro:~ dovnimratz$ cd /Applications/eclipse\ 3/Dov-Nimratzs-MacBook-Pro:eclipse 3 dovnimratz$ ./eclipse -vm /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/bin/java core_dump
Wed Sep 28 09:47:29 Dov-Nimratzs-MacBook-Pro.local eclipse[4987] <Error>: kCGErrorIllegalArgument: CGSShapeWindow
Wed Sep 28 09:47:29 Dov-Nimratzs-MacBook-Pro.local eclipse[4987] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.