From: Geoff McLane <ubuntu@geoffair.info>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] debugging output to a file
Date: Wed, 13 Jan 2016 20:05:29 +0100 [thread overview]
Message-ID: <56969FF9.30402@geoffair.info> (raw)
In-Reply-To: <20160013035742.eklhad@comcast.net>
Hi Karl,
As you predicted can not compile in windows... missing
'setlinebuf(FILE *file)' ;=((
What exactly does it do?
Since you mention "to make sure the log is up to date",
so is it like a flush?
In a segfault like crash quite often the last lines do not
get to the log... and of course they are usually the lines
we need to see most... but a fflush after a write fix this...
mostly...
Regards,
Geoff.
next prev parent reply other threads:[~2016-01-13 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 8:57 Karl Dahlke
2016-01-13 19:05 ` Geoff McLane [this message]
2016-01-13 19:23 ` Geoff McLane
2016-01-16 14:46 ` Adam Thompson
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=56969FF9.30402@geoffair.info \
--to=ubuntu@geoffair.info \
--cc=edbrowse-dev@lists.the-brannons.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.
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 NNTP newsgroup(s).