From: Shriramana Sharma <samjnaa@gmail.com>
To: Linux C Programming List <linux-c-programming@vger.kernel.org>
Subject: Re: Curious segmentation fault - please help
Date: Sun, 14 May 2006 00:28:13 +0530 [thread overview]
Message-ID: <200605140028.17718.samjnaa@gmail.com> (raw)
In-Reply-To: <6a00c8d50605131020o6665b157u18b72e93cc04411b@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
Saturday 13 May 2006 22:50 samaye, Steve Graegert alekhiit:
> > vaasara[6] does give the correct output. The fault is seen *after*
> > vaasara[6] is read and written to stdout:
>
> which accesses the last element correctly. Nevertheless, the function
> tries to read one more character causing a segfault. Please don't
> misinterpret valgind's output: we are still in listsplpanchaanga().
Of course. But all I am doing is using the standard fprintf function. Is it
possible that the behaviour of this function would have changed from glibc
2.36 to glibc 2.4?
> Hm, don't know what could have changed. I am not a SuSEr anymore;
> returned to Debian and NetBSD.
So can't see you anymore on SLE?
--
Tux #395953 resides at http://samvit.org
playing with KDE 3.51 on SUSE Linux 10.1
$ date [] CCE +2006-05-14 W19-7 UTC+0530
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-05-13 18:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 14:28 Curious segmentation fault - please help Shriramana Sharma
2006-05-13 15:09 ` Steve Graegert
2006-05-13 16:27 ` Shriramana Sharma
2006-05-13 17:20 ` Steve Graegert
2006-05-13 18:58 ` Shriramana Sharma [this message]
2006-05-13 21:04 ` Steve Graegert
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=200605140028.17718.samjnaa@gmail.com \
--to=samjnaa@gmail.com \
--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).