From: Kurt Kehler <kmk@pa.net>
To: linux-c-programming@vger.kernel.org
Subject: Re: Segmentation fault
Date: Tue, 16 Apr 2002 15:30:40 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.10.10204160232390.587-100000@darkstar.example.net> (raw)
In-Reply-To: <OF5DFD5B6D.7D47A4C9-ON65256B98.0022D8F5@pune.tcs.co.in>
On Thu, 11 Apr 2002, Hemant Mohan wrote:
> I compiled this code with gcc-3.0.3 and ran it. It displays the output as:
>
> Easter in 2002 on 3/31
>
> There was no segmentation fault or any other messages. Attachment easter.c
> contains the source code with a small modification from yours. I only moved
> the #include <stdio.h> line before the definition of easter().
Hemant,
Thanks for taking the time to do this. Moving the #include <stdio.h> did
not prevent the segmentation fault.
Kurt Kehler
next parent reply other threads:[~2002-04-16 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF5DFD5B6D.7D47A4C9-ON65256B98.0022D8F5@pune.tcs.co.in>
2002-04-16 19:30 ` Kurt Kehler [this message]
[not found] <20020411084352.65e693fe.subscript@free.fr>
2002-04-16 19:30 ` Segmentation fault Kurt Kehler
[not found] <1328439575.20020411104849@kgpa.ru>
2002-04-16 19:29 ` Kurt Kehler
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=Pine.LNX.4.10.10204160232390.587-100000@darkstar.example.net \
--to=kmk@pa.net \
--cc=linux-c-programming@vger.kernel.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 NNTP newsgroup(s).