[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[List Home]
|
Re: [cdt-dev] Error logged from Debug Core when I run my executable
|
- From: James Blackburn <jamesblackburn@xxxxxxxxx>
- Date: Tue, 1 Jun 2010 16:34:41 +0100
- Delivered-to: cdt-dev@eclipse.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=3TFBe0NU3RLX91QztDzz7CxSLXf0QmOR1CBvtwdyvlI=; b=iJ0NL4DkJa63P62yWp4cWTfAs2uzLPef0E7Hqj3d5XqIt/ejbSH+UwdhUjq/RvVK0S NpySCU0jkH34WzPMcZ9qHTh1dfGx5PLuLwSUItQAEjy0rKgYB+A7FFlaJQfpgMNAovYB TUCeWdUgBxiLf3ieB8k63laVbzx1pL5dNSD3w=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=iHce4IyJHhb80cfqIJxg7zonjeYODPZlSX+hs49V3U8YqUUeMnw57MbmYuuBoaFpCR qvBjMFrHBiZMCXi1Hv82xS80pa1U/IviKMIgDKkGwfP/eQC0N8nq4hmAxAsEh+dGM3N2 mvtXwLkArYsMFfZ2VJc96F/9SqUemeB2GYKFE=
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
>