Re: 2^n (was: weird g++ behavior)

2002-11-23 Thread Bryan Jurish
On 22 November 2002 at 21:14:00, Michael Heironimus wrote: > > or is it just a swing-a-dead-chicken- > > over-your-head-at-midnight-on-a-new-moon-whilst- > > invoking-eldritch-and-mystic-powers sort of thing? > > It could be a board/BIOS problem, or it could be that one of those two > modul

Re: 2^n (was: weird g++ behavior)

2002-11-22 Thread Tom Cook
On 0, Michael Heironimus <[EMAIL PROTECTED]> wrote: > If you have time it might be to your advantage to go ahead and run a > real memory test. If one of those modules does have a problem you'd be > better off finding out now instead of later when it causes some other > strange problem. If you can'

Re: 2^n (was: weird g++ behavior)

2002-11-22 Thread Michael Heironimus
On Sat, Nov 23, 2002 at 02:59:38AM +0100, Bryan Jurish wrote: > i can definitely live with this, but can anyone explain > to me why this must be so? (mainboard/bios bug is my > personal guess, but i'm truly stumped...) did some > goofball go and assume that everyone on the planet has > 2^n bytes

2^n (was: weird g++ behavior)

2002-11-22 Thread Bryan Jurish
hi Elizabeth, hi list, first of all, thanks for your suggestions, Elizabeth -- a 'crashme.sh' script was in fact very helpful... turns out, the machine (same procedure on another box ran fine) crashed g++ only with my 256MB ram-bar in slot-0 and my 512MB bar in slot-1 ... go figure. each bar al

Re: weird g++ behavior

2002-11-21 Thread Bryan Jurish
hi Elizabeth, On 21 November 2002 at 11:30:10, Elizabeth Barham wrote: > What about running conftest.cc through the pre-processor with the "-E" > option (g++ -E ...)? That often helps clear up some of the odder parse > errors. > > Elizabeth yes, i also find it a good way to diagnose weird

Re: weird g++ behavior

2002-11-21 Thread Elizabeth Barham
What about running conftest.cc through the pre-processor with the "-E" option (g++ -E ...)? That often helps clear up some of the odder parse errors. Elizabeth -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: weird g++ behavior

2002-11-21 Thread Bryan Jurish
On 21 November 2002 at 09:08:27, Elizabeth Barham wrote: > I had somewhat similar problems with some standard libraries > (libstdc++, libc, etc.) accidentally left in /usr/local after upgrading > to woody. Removing the libraries and executables remedied the > situation. > > Elizabeth hmm,

Re: weird g++ behavior

2002-11-21 Thread Elizabeth Barham
I had somewhat similar problems with some standard libraries (libstdc++, libc, etc.) accidentally left in /usr/local after upgrading to woody. Removing the libraries and executables remedied the situation. Elizabeth -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe".

weird g++ behavior

2002-11-21 Thread Bryan Jurish
greetings all, a few months ago, i made the great leap of faith and switched to debian (woody) from suse -- a few false starts, but all in all i'm still convinced it was a good choice, if only... my problem is that i'm getting a whole slew of intermittent, unreproducable (but nonetheless frequen