From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: Stuart Longland <stuartl@longlandclan.hopto.org>
Cc: Arash Farmand <arashfarmand@hotmail.com>, gcc-help@gcc.gnu.org
Subject: Re: gcc
Date: Mon, 31 Mar 2003 13:28:00 -0000 [thread overview]
Message-ID: <vpqu1dkt0s9.fsf@imag.fr> (raw)
In-Reply-To: <3E87EE8F.4070104@longlandclan.hopto.org> (Stuart Longland's message of "Mon, 31 Mar 2003 17:30:23 +1000")
Stuart Longland <stuartl@longlandclan.hopto.org> writes:
> Not sure about it not appearing at all. I think it would appear when
> the program ends, but then again, I may be wrong.
If the program ends properly, I think the output *has* to be flushed,
(At least, it does in most cases) but for example, if your program
makes a segfault, you will probably loose the contents of the output
buffer.
in
printf("Hello\n");
f();
printf("world");
g();
if the output is just "Hello", and segmentation fault, the crash may
have occured in f() or g() ...
That's why its generally a good advice to put "\n" at the end of any
debug/test output.
--
Matthieu
next prev parent reply other threads:[~2003-03-31 8:09 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 1:45 gcc Arash Farmand
2003-03-31 2:28 ` gcc Andre Kirchner
2003-03-31 7:31 ` gcc Matthieu Moy
2003-03-31 8:09 ` gcc Stuart Longland
2003-03-31 13:28 ` Matthieu Moy [this message]
2003-04-02 0:42 ` gcc Segher Boessenkool
-- strict thread matches above, loose matches on Subject: below --
2023-02-28 12:55 gcc Octavia Bennett
2022-11-03 14:56 gcc Jason Bloom
2021-11-26 9:24 gcc Claire Carter
2021-07-22 4:31 Gcc Alice Matthews
2021-07-14 19:25 Gcc Wendy Bonner
2020-11-07 18:08 gcc Simon Liu
2019-12-16 8:50 Gcc Isabella Kathryn
2012-06-07 9:36 gcc jai singh
2012-06-07 12:27 ` gcc Jonathan Wakely
2011-08-29 8:44 GCC emil johansson
2011-08-29 9:29 ` GCC David Brown
2011-08-29 16:32 ` GCC Philip Herron
2008-10-09 21:38 gcc Jair Santos
2008-10-10 10:24 ` gcc Andrew Haley
2006-06-03 10:24 gcc Gunnar Sjoo
2004-09-22 4:27 GCC Drew Gray
2004-09-22 12:48 ` GCC Ishwar Rattan
2004-03-25 23:13 gcc frostflare
2004-03-26 1:12 ` gcc Eljay Love-Jensen
2004-03-25 19:12 gcc frostflare
2004-03-25 19:13 ` gcc llewelly
2004-03-24 15:05 gcc faltat
2004-03-24 22:32 ` gcc Ken Foskey
2004-03-24 2:44 GCC faltat
2004-03-24 4:23 ` GCC Eljay Love-Jensen
2003-12-16 14:14 GCC Jerry Lyle
2003-09-04 20:55 gcc Rich Franczak
2003-09-04 23:42 ` gcc Eljay Love-Jensen
2003-03-31 7:19 gcc Dockeen
2003-03-30 7:24 gcc Arash Farmand
2003-03-30 15:50 ` gcc Bharathi S
2003-03-31 0:58 ` gcc LLeweLLyn Reese
[not found] <616BE6A276E3714788D2AC35C40CD18D86F76D@whale.softwire.co.uk>
2002-10-11 5:13 ` GCC Rupert Wood
2002-10-11 4:44 GCC Bruno Aulagner
2002-08-29 19:23 gcc Samuel Lee Kwek Ming
2002-08-29 19:27 ` gcc Ish Rattan
2002-08-30 3:42 ` gcc Claudio Bley
2002-08-19 19:23 gcc Samuel Lee Kwek Ming
2002-01-10 9:30 gcc Tom Fetterer
2001-02-15 7:50 gcc Robert Neal
2001-02-15 9:16 ` gcc Alexandre Oliva
2001-02-12 17:17 gcc Paramjit Cheema
2001-02-12 18:38 ` gcc Alexandre Oliva
2001-01-21 19:26 gcc Simon Ouellet
2001-01-21 19:48 ` gcc Alexandre Oliva
2000-05-29 8:16 gcc Blythe Dickman
2000-05-29 10:15 ` gcc Martin v. Loewis
2000-03-09 11:33 gcc Olaf Miller
2000-03-09 16:43 ` gcc Martin v. Loewis
2000-04-01 0:00 ` gcc Martin v. Loewis
2000-04-01 0:00 ` gcc Olaf Miller
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=vpqu1dkt0s9.fsf@imag.fr \
--to=matthieu.moy@imag.fr \
--cc=arashfarmand@hotmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=stuartl@longlandclan.hopto.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).