Re: Curious segmentation fault - please help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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: pgp8ASHyV6eOq.pgp
Description: PGP signature


[Index of Archives]     [Linux Assembler]     [Git]     [Kernel List]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [C Programming]     [Yosemite Campsites]     [Yosemite News]     [GCC Help]

  Powered by Linux