2009/3/19 Jack Repenning <jrepenning_at_collab.net>:
> Today, I fire up the debugger again, and ... everything works just
> fine. No rebuilds of any kind in between. No reboots of any kind in
> between. I am, today, working on a new launch of my app, but I had
> killed and relaunched it several times, last night. All runs,
> successful and failing, were under the Xcode IDE and gdb debugger, and
> I am also, today, working on a new launch of the IDE, and I don't
> recall restarting it yesterday, so it's possible the variation is the
> IDE's fault.
> Today (but not yesterday, sadly), I have used Activity Monitor's list
> of open files to confirm that my app has open only APR 1.x libraries.
Was it rainy yesterday? Can it be some network problems?
"APR does not understand this error code" is (looking into APR
sources, /misc/unix/errorcodes.c), just a more wordy equivalent
of "unknown error code". The apr_strerror() function (or native_strerror()
called by it) returns this message.
Whoever called that apr_strerror() should know the context where the
issue occurred and the actual code. Were those included in the message,
or it just relied on the standard message being available?
And without knowing the code it is impossible to know in what error code
range it falls, and whether it is the same every time.
The following thread came up on Apache Tomcat webserver Users' list
yesterday. It caught me, that the title mentions this apr message,
though I think there is no other relation to this very problem.
Received on 2009-03-20 01:46:06 CET