[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] unexec() for Cygwin port
From: |
Eli Zaretskii |
Subject: |
Re: [PATCH] unexec() for Cygwin port |
Date: |
30 Mar 2004 08:20:10 +0200 |
> From: Stefan Monnier <address@hidden>
> Date: 29 Mar 2004 16:10:02 -0500
>
> The macosx code also spits lots of "debug" output when dumping
> and noone has complained about it. I don't see any problem with that.
I was under the impression that some printf's are really left-overs;
in particular, some of them there are in the normal execution path,
i.e. when there's no failure in sight. Perhaps you should take a look
at the code yourself.
It is IMHO also advisable to figure out which of these printf's should
really be converted into calls to `abort', since in some grave cases,
a mere printf wouldn't give enough info to debug the problem.
> Especially during pretest.
What pretest?
Re: [PATCH] unexec() for Cygwin port, Richard Stallman, 2004/03/29