Hi everybody... <br />I need a clue...Maybe someone of you has something to suggest :) <br />I'm developing a server
withmico and postgresql in c++... The access to postgresql <br />is done using libpq, not via corba...The compiler I
useis gcc-2.95-2 <br />The operating systems are Linux and Solaris 2.7. <br />On Solaris I'm trying to use Purify 5.1
butit founds a memory segment error <br />during mico initialization and my program dumps core. Then I've get out mico
andeven Xerces (an XML parser) out of the server but then purify complains about an error in a an fstream function,
like:<br /> IPR: Invalid pointer read <br /> This is occurring while in: <br />
ifstream::~ifstream()[fstream.cc:110] <br /> { <br /> return "w"; <br />
}<br /> => #endif <br /> Configuration::loadConfig(const char*) [Configuration.o] <br
/> DSControl_impl::start() [ds_sds_nocorba_impl.o] <br /> main [ds_sds_nocorba_main.o]
<br/> _start [crt1.o] <br /> Reading 4 bytes from 0xff1927a4 between the heap and the stack.
<p>I'vebeen forced to use libpq from version 6.5.3 because if I link the 7.0.2 <br />version in then I get an error
froma function inside PostgreSQL setdb <br />The error is always the same: the program is accessing an area between the
<br/>heap and the stack......but just migrates around corba, ifstream, postgres..... <br />Well... Before I go
squashingmy head on the wall again, dou you have an idea on <br />how to get more info on this ?????????? <br />I know
thisis a bit OT here, because I don't think postgres is really involved in this, <br />simply I don't know what to do
withthis... Could it be simply a purify problem ???? <br />The system seems to work fine without it....(seems......)
<p>Thanksfor your patience.... <br /> Fabrizio <pre>--
Fabrizio Sciarra ! Tel +39 050 545 111
Intecs sistemi spa ! Fax +39 050 545 200
via Gereschi 32-34, 56100 Pisa ITALY. ! fabrizio@pisa.intecs.it
-- My opinions are mine, not necessarly of my employers --
* Linux. The choice of a GNU generation
* Java Lobby Member * Ada community member.</pre>
