public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "David B. Rees" <dbr@spoke.nols.com>
To: egcs@egcs.cygnus.com
Subject: fstream, egcs, and seg faults
Date: Mon, 15 Mar 1999 18:19:00 -0000	[thread overview]
Message-ID: <XFMail.990315181911.dbr@spoke.nols.com> (raw)

This may be offtopic, but I'm hoping someone here has come across this problem
before and has a solution.  I searched the last two months of egcs archives with
no luck.

The following two programs will segfault on my Linux machine:

#include <fstream.h>
void main(void)
{
        ifstream *IS;
        IS = new ifstream("test.cpp");
}

#include <fstream.h>
void main(void)
{
        ifstream IS;
        char line[256];
        IS.open("test.cpp");
        IS.getline(line, 255);
}

I came across this problem while trying to compile VTK on my machine.  I
searched dejanews for similar reports, and came across a few people who had. 
Here's the versions of software I'm running:

spoke:~> g++ -v
Reading specs from /usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)

glibc2.1, Binutils 2.9.1.0.21, kernel 2.2.3

glibc hasn't been recompiled with a glibc2.1 compiled compiler.


Any ideas?  Should I attempt recompiling glibc2.1?

Thanks,
Dave

WARNING: multiple messages have this Message-ID
From: "David B. Rees" <dbr@spoke.nols.com>
To: egcs@egcs.cygnus.com
Subject: fstream, egcs, and seg faults
Date: Wed, 31 Mar 1999 23:46:00 -0000	[thread overview]
Message-ID: <XFMail.990315181911.dbr@spoke.nols.com> (raw)
Message-ID: <19990331234600.D6gzt-zJOF50OeWa68-RGNPOtMZMWogUet1AWoG1-9k@z> (raw)

This may be offtopic, but I'm hoping someone here has come across this problem
before and has a solution.  I searched the last two months of egcs archives with
no luck.

The following two programs will segfault on my Linux machine:

#include <fstream.h>
void main(void)
{
        ifstream *IS;
        IS = new ifstream("test.cpp");
}

#include <fstream.h>
void main(void)
{
        ifstream IS;
        char line[256];
        IS.open("test.cpp");
        IS.getline(line, 255);
}

I came across this problem while trying to compile VTK on my machine.  I
searched dejanews for similar reports, and came across a few people who had. 
Here's the versions of software I'm running:

spoke:~> g++ -v
Reading specs from /usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)

glibc2.1, Binutils 2.9.1.0.21, kernel 2.2.3

glibc hasn't been recompiled with a glibc2.1 compiled compiler.


Any ideas?  Should I attempt recompiling glibc2.1?

Thanks,
Dave

             reply	other threads:[~1999-03-15 18:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-15 18:19 David B. Rees [this message]
     [not found] ` < XFMail.990315181911.dbr@spoke.nols.com >
1999-03-16 15:46   ` Martin v. Loewis
     [not found]     ` < 199903162344.AAA00748@mira.isdn.cs.tu-berlin.de >
1999-03-17 11:40       ` (OFFTOPIC?) fstream, egcs, glibc2.1 " David B. Rees
     [not found]         ` < XFMail.990317114016.dbr@spoke.nols.com >
1999-03-17 11:49           ` David Edelsohn
1999-03-31 23:46             ` David Edelsohn
1999-03-17 15:23           ` Martin v. Loewis
1999-03-31 23:46             ` Martin v. Loewis
1999-03-31 23:46         ` David B. Rees
1999-03-31 23:46     ` fstream, egcs, " Martin v. Loewis
1999-03-31 23:46 ` David B. Rees

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=XFMail.990315181911.dbr@spoke.nols.com \
    --to=dbr@spoke.nols.com \
    --cc=egcs@egcs.cygnus.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 read-only IMAP folder(s) and NNTP newsgroup(s).