From: Eli Zaretskii <eliz@elta.co.il>
Cc: emacs-devel@gnu.org, jbuehler@hekimian.com
Subject: Re: [PATCH] unexec() for Cygwin port
Date: 30 Mar 2004 08:20:10 +0200 [thread overview]
Message-ID: <uoeqeyhyd.fsf@elta.co.il> (raw)
In-Reply-To: <m1ad1ze4yu.fsf-monnier+emacs@empanada.iro.umontreal.ca> (message from Stefan Monnier on 29 Mar 2004 16:10:02 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> 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?
next prev parent reply other threads:[~2004-03-30 6:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 13:38 [PATCH] unexec() for Cygwin port Joe Buehler
2004-03-29 19:27 ` Eli Zaretskii
2004-03-29 20:38 ` Joe Buehler
2004-03-29 21:10 ` Stefan Monnier
2004-03-30 6:20 ` Eli Zaretskii [this message]
2004-03-30 10:04 ` What Pretest? (was Re: [PATCH] unexec() for Cygwin port) Kim F. Storm
2004-03-30 6:13 ` [PATCH] unexec() for Cygwin port Eli Zaretskii
2004-03-30 6:24 ` Eli Zaretskii
2004-03-30 3:53 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2004-03-29 13:32 Joe Buehler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uoeqeyhyd.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jbuehler@hekimian.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.