Re: cout & Performer crashes

New Message Reply Date view Thread view Subject view Author view

Dirk Luesebrink (crux++at++artcom.de)
Tue, 05 Aug 1997 04:09:42 -0400

the topic was fully discussed on the mailing list quit a while ago. the
problem arises from static global variable initialization in 'C++'.
iostream lib has some of them. when linking a 'C++' app the 'C' linker
puts not the right start-up code in your executable. you can see that at
your call stack when you dbx: stop in main.

1 main(argc = 1, argv = 0x7fff2f64)
["/usr/people/ethan/midas/tinyMidas/tinyMidas.c++":29, 0x42579c]
2 __istart() ["crt1tinit.s":13, 0x425700

__istart is 'C' start up. for C++ you would see __start i think.

/usr/bin/CC and and /usr/bin/cc are just the front end to the various
phases of the compilation linking process. the linker is
/usr/lib/ld -> ../lib/driverwrap. /usr/bin/cc simply fails to instruct
the linker to setup the right 'C++' start up code. iostream and stdio
works fine together.

in pages full of warnings its easy to overlook that most of the
Performer Makefile tend to use /usr/bin/cc instead of /usr/bin/CC for
the linking phase. linking 'C' apps with /usr/bin/CC never was a problem
for me, but for sure, some performer purists are spotting some
performance differences in the executables.

dirk.

Swaminathan N. wrote:
>
> On Mon, 4 Aug 1997, Scott McMillan wrote:
>
> >
> > > >
> > > > Any ideas why cout doesn't work?
> > > > has anyone else had this problem?
> > >
> > > Stick in Iostream_init() just after pfInit()
> > >
> > > Swami
> >
> > I am pretty sure this very problem was discussed in this group a few _years_
> > ago. If memory serves...
> >
> > I still think the original poster was _LINKING_ (not compiling) with cc.
> > This call to Iostream_init() should not be necessary if linked with CC.
> >
>
> This is an area where I'm very fuzzy about, trying stuff till it works and
> never bothering to find out why it didn't work. The original poster said that
> he had linked with CC, and not cc, if I'm not mistaken, which is why I threw
> in the Iostream_init() suggestion.
>
> I can vouch for the fact the it is not only a linking issue, since my app
> core dumps without Iostream_init(), and I'm linking with CC.
>
> I remember reading vaguely about observing caution when using stdio with
> iostream. Maybe the real reason lies there. I'll try to track it down.
>
> bye
> Swami
>
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> v Swaminathan Narayanan ^
> v swami++at++evl.uic.edu ^
> v Office: 996-3002 ^
> v Home: 850-2726 ^
> v http://www.evl.uic.edu/swami ^
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> =======================================================================
> List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
            Submissions: info-performer++at++sgi.com
        Admin. requests: info-performer-request++at++sgi.com

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:55:42 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.