This is the mail archive of the
mailing list for the frysk project.
Re: PTraceByteBuffer vs errno
- From: Andrew Cagney <cagney at redhat dot com>
- To: Mark Wielaard <mark at klomp dot org>
- Cc: frysk at sources dot redhat dot com
- Date: Thu, 03 Aug 2006 10:38:10 -0400
- Subject: Re: PTraceByteBuffer vs errno
- References: <email@example.com>
Mark Wielaard wrote:
Hi,I'm draining my mail backlog.
While investigating some strange RuntimeExceptions (indicating
interrupted system calls) coming from PTraceByteBuffer I noticed that it
does its own errno handling when calling the Ptrace class. This seems
incorrect since Ptrace a) does its own errno handling and will throw the
appropriate exception when errno is set and b) Ptrace is not just a
simple call, but a complex chaining of calls through multiple threads so
the errno value set might not be related at all to the original errno
call. So I propose to remove all errno handling from PtraceByteBuffer.
This also made my local breakpoint tests become more predictable.
Mark, yes definitely, good catch (I'm assuming this was committed).