public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jakob Østergaard" <jakob@unthought.net>
To: Sean Van Buggenum <sv24@uow.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel or std c++ libraries
Date: Sun, 21 Oct 2001 14:58:29 +0200	[thread overview]
Message-ID: <20011021145828.A4292@unthought.net> (raw)
In-Reply-To: <200110210150.LAA14611@isis.its.uow.edu.au>
In-Reply-To: <200110210150.LAA14611@isis.its.uow.edu.au>; from sv24@uow.edu.au on Sun, Oct 21, 2001 at 11:50:22AM +1000

On Sun, Oct 21, 2001 at 11:50:22AM +1000, Sean Van Buggenum wrote:
> Hi ,                                                                  
> I think there's a bug with .. i guess the linux kernel... or standard 
> c++ libraries included with recent installations of mandrake and      
> redhat.                                                               
> I've come to this conclusion because something i've written in c++,   
> very basic stuff... ( using the function seekg() from the fstream     
> library ) works fine on unix installations that i've used, but not on 
> any of the linux installations i've tried on My computer. All the code
>                                                                       
> does is open a binary file with the file pointer set for however many 
> positions from the END of the file (it works when i use the start of  
> the file ) .. and try to read from there.                             
> i've used kernel 2.2.16.... and it didn't work then.. i've recently   
> installed mandrake 8.1 and thought that with the newer kernel         
> included (hoped) it was just a bug in the redhat installation that i  
> had previously. But it still doesn't work.                            
> Is it a bug in the software ? or something to do with my hardware..is 
> what i'd like to know.. i'm using a intel celeron 600 processor.. if  
> that'd be important.                                                  

No the CPU is not important (at this stage anyway).

Tell us:  kernel version, glibc version, compiler version, stdlibc++ version.

And send the code too. (If you can't or won't, or if the code is lenghty, write
up a small program to reproduce the error and send the code for that one
instead).

It's probably a stdlibc++ bug.  If it's a glibc bug or a kernel bug, the same
error can be reproduced in C too - can it ?

-- 
................................................................
:   jakob@unthought.net   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:

      reply	other threads:[~2001-10-21 12:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-21  1:50 kernel or std c++ libraries Sean Van Buggenum
2001-10-21 12:58 ` Jakob Østergaard [this message]

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=20011021145828.A4292@unthought.net \
    --to=jakob@unthought.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sv24@uow.edu.au \
    /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