From: Andrew Cottrell Newsgroups: comp.os.msdos.djgpp Subject: Re: debbuging with rhide. NOT. :( Date: Sun, 24 Nov 2002 19:41:56 +1100 Organization: ECLiPSE Lines: 36 Message-ID: References: NNTP-Posting-Host: p141-tnt7.syd.ihug.com.au Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: lust.ihug.co.nz 1038127326 22533 203.173.144.141 (24 Nov 2002 08:42:06 GMT) X-Complaints-To: abuse AT ihug DOT co DOT nz NNTP-Posting-Date: Sun, 24 Nov 2002 08:42:06 +0000 (UTC) X-Newsreader: Forte Agent 1.92/32.572 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com >Yo! > >Is it really that noone has any ideas? creepy.. > >btw (not quite) it seems terribly awfully that removing > >fstream (not the header but the only declaration of one) > >well.. huh.. > >fstream bin, ban; > >gets debbugging working again. However, i somehow wouldn't like to do it for >my code sortof uses it. Okay now we know you are using C++ and GCC 3.2 at a guess (not 2.9.5.3). If you are not using Rhide 1.5.0 snapshot from 28-Aug-2002 or later then go and grab it at www.rhide.com Please read the readme.txt file that comes with GCC 3.2. If you are using Rhide 1.5.0 28-Aug-2002 snapshot and GCC 3.2 then please lgive a small example program, < 20-30 lines. If you are using C++ make sure you do not mix object files from different GCC versions, even 3.1 to 3.2 is different. C objects as far as I know are okay between the major versions, ie you can mix 3.1 and 3.2 C objects. Please supply more info in the future when you have a problem and please remember that no one gets paid for this so support may take a while.