Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 231815 - [console] Exception when closing PTY stream
Summary: [console] Exception when closing PTY stream
Status: CLOSED DUPLICATE of bug 286162
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 6.0   Edit
Hardware: PC Linux
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Marc Khouzam CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-13 09:59 EDT by Marc Khouzam CLA
Modified: 2011-04-01 05:12 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Khouzam CLA 2008-05-13 09:59:33 EDT
See bug 231686

Pawel wrote:
I got the following exception for no particular reason (which
uncovered this bug):

java.io.IOException: close error
        at
org.eclipse.cdt.utils.pty.PTYInputStream.close(PTYInputStream.java:79)
        at java.io.BufferedInputStream.close(BufferedInputStream.java:440)
        at
org.eclipse.debug.internal.core.OutputStreamMonitor.read(OutputStreamMonitor.java:183)
        at
org.eclipse.debug.internal.core.OutputStreamMonitor.access$1(OutputStreamMonitor.java:134)
        at
org.eclipse.debug.internal.core.OutputStreamMonitor$1.run(OutputStreamMonitor.java:207)
        at java.lang.Thread.run(Thread.java:595)

Marc replied:
Looking at the code, it seems to originate from the
native method close0() called from
org.eclipse.cdt.utils.pty.PTYInputStream.close().  My only thought is that
maybe there is a threading issue and the same PTY stream is closed twice at the
same time: the first time by the Debug Platform which is monitoring the stream
(OutputStreamMonitor) and in a separate thread in MIInferiorProcess.

I'm not sure how mutli-threads are handled with the Debug Platform.  Maybe we
can discuss.
Comment 1 Anton Leherbauer CLA 2011-04-01 05:12:14 EDT

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