From: "Stefan Monnier" <monnier+gnu.emacs.bug/news/@RUM.cs.yale.edu>
Subject: Re: `print' does not print
Date: 22 Mar 2002 15:44:27 -0500 [thread overview]
Message-ID: <5lg02s8h90.fsf@rum.cs.yale.edu> (raw)
In-Reply-To: 15515.28200.228210.321561@jupiter.akutech-local.de
>>>>> "Ralf" == Ralf Fassel <ralfixx@gmx.de> writes:
> If I put at the start of main:
> write(1,"write\n",6);
> fwrite("frwite\n", 7,1,stdout);
> I see the `write', but not the fwrite when I compile with gcc. I see
> both when I compile with cc.
It looks like the problem is that the `stdout' FILE* stuff got wedged.
Could you look at `stdout' ? Maybe it got mangled during dump ?
Maybe it's an interaction between malloc (or mmap) and dumping (assuming
the `stdout' buffer was allocated with malloc).
Has any part of the dumping or memory management been changed between
21.1 and 21.2 ?
Stefan
_______________________________________________
Bug-gnu-emacs mailing list
Bug-gnu-emacs@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs
next prev parent reply other threads:[~2002-03-22 20:44 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200203202019.g2KKJfs4410490@jupiter.akutech-local.de>
[not found] ` <ap3lmcnkjy4.fsf@fosters.umd.edu>
2002-03-21 16:25 ` `print' does not print Eli Zaretskii
2002-03-21 17:10 ` D. Goel
2002-03-21 18:49 ` Ralf Fassel
2002-03-21 20:15 ` Ralf Fassel
2002-03-21 21:14 ` Ralf Fassel
2002-03-22 10:17 ` Eli Zaretskii
2002-03-22 10:41 ` Ralf Fassel
2002-03-22 11:58 ` Eli Zaretskii
2002-03-22 14:22 ` Ralf Fassel
2002-03-22 17:00 ` Eli Zaretskii
2002-03-22 17:47 ` Ralf Fassel
2002-03-22 18:35 ` Eli Zaretskii
2002-03-22 19:17 ` Ralf Fassel
2002-03-22 20:11 ` Eli Zaretskii
2002-03-22 22:18 ` Ralf Fassel
2002-03-23 8:54 ` Eli Zaretskii
2002-03-23 14:19 ` Ralf Fassel
2002-03-23 16:48 ` Eli Zaretskii
2002-03-23 17:10 ` Ralf Fassel
2002-03-22 20:44 ` Stefan Monnier [this message]
2002-03-23 16:13 ` Richard Stallman
2002-03-24 16:51 ` Ralf Fassel
2002-03-24 18:16 ` Eli Zaretskii
2002-03-24 20:22 ` Ralf Fassel
2002-03-25 6:02 ` Eli Zaretskii
2002-03-25 13:47 ` Ralf Fassel
2002-03-25 14:35 ` Eli Zaretskii
2002-03-25 14:49 ` David Kaelbling
2002-03-25 20:05 ` Eli Zaretskii
2002-03-25 20:15 ` David Kaelbling
2002-03-26 5:46 ` Eli Zaretskii
2002-03-26 14:20 ` David Kaelbling
2002-03-26 14:28 ` Eli Zaretskii
2002-03-26 14:43 ` Ralf Fassel
2002-03-25 17:41 ` Ralf Fassel
2002-03-25 17:55 ` David Kaelbling
2002-03-25 20:14 ` Eli Zaretskii
2002-03-25 21:33 ` Ralf Fassel
2002-03-26 5:48 ` Eli Zaretskii
2002-03-26 14:43 ` David Kaelbling
2002-03-26 17:30 ` Ralf Fassel
2002-03-27 5:49 ` Eli Zaretskii
2002-03-27 9:00 ` Ralf Fassel
2002-03-27 9:10 ` Eli Zaretskii
2002-04-12 9:37 ` Eli Zaretskii
2002-04-12 11:31 ` Ralf Fassel
[not found] ` <15542.50594.404120.372721@jupiter.akutech-local.de>
2002-04-12 15:08 ` David Kaelbling
2002-04-13 10:33 ` Eli Zaretskii
2002-04-13 10:52 ` Eli Zaretskii
2002-04-13 19:06 ` Richard Stallman
2002-03-25 12:01 ` Richard Stallman
2002-03-22 12:24 ` Richard Stallman
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=5lg02s8h90.fsf@rum.cs.yale.edu \
--to=monnier+gnu.emacs.bug/news/@rum.cs.yale.edu \
/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.