Re: [cdt-dev] Error logged from Debug Core when I run my executable

[Pawel Piech <pawel.piech@xxxxxxxxxxxxx>]

Hi Jeff,
Please file a bug for Debug Platform.

Thanks,
Pawel

On 06/01/2010 08:34 AM, James Blackburn wrote:
> Taking a look at this debug.core OutputStreamMonitor does:
>
> try {
>     ...
>     fStream.read(...);
>     ...
> } catch (IOException e) {
>     if (!fKilled) {
> 	DebugPlugin.log(ioe);
>      }
>     return;
> }
>
> So it seems the exception shouldn't be logged during tear down. But
> fKilled ins't volatile (and there isn't any synchronisation) so that's
> likely part of the problem...
>
> Cheers,
> James
>
> On 31 May 2010 22:52, Jeff Johnston<jjohnstn@xxxxxxxxxx>  wrote:
>    
> > We have been getting the following exception logged in the Error log for
> > some time when we run a Linux Autotools project executable from the Binaries
> > folder using "Run as C/C++ application".  I choose gdb/mi when prompted and
> > get:
> >
> > Error logged from Debug Core
> > java.io.IOException: read error
> > at org.eclipse.cdt.utils.spawner.SpawnerInputStream.read0(Native Method)
> > at
> > org.eclipse.cdt.utils.spawner.SpawnerInputStream.read(SpawnerInputStream.java:66)
> > at java.io.BufferedInputStream.read1(BufferedInputStream.java:273)
> > at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
> > at java.io.FilterInputStream.read(FilterInputStream.java:107)
> > at
> > org.eclipse.debug.internal.core.OutputStreamMonitor.read(OutputStreamMonitor.java:144)
> > 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:636)
> >
> > The executable runs fine.
> >
> > This is happening with the current Helios RC2 package:
> >
> > http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/helios/RC2/eclipse-linuxtools-helios-RC2-incubation-linux-gtk.tar.gz
> >
> > I have seen the same error reported a while back for PTP by Beth Tibbits but
> > no real answer as to why it occurs and how to stop it.
> >
> > As mentioned, the executable runs fine until completion and the error does
> > not affect subsequent tasks/actions, but it would be nice to know why this
> > is happening only for an Autotools project and not for a Managed Make
> > project.
> >
> > Any thoughts/ideas?
> >
> > -- Jeff J.
> >
> >
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >
> >      
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>