Sounds like it might be related to http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15645
Niklas
hi niklas
many thanks for your reply, i can't respond to your post directly as it never appeared in my inbox for some reason.
that gcc bug does look suspicious but i've investigated thoroughly and concluded that it's not the explanation -
1) the gcc bug is triggered with ...
ostringstream s1; s1 << internal << setw(2) << 0;
... the int must be a literal zero - whereas Calc crashes with ...
std::ostringstream s1; s1 << 5;
... and the int can be any value.
2) my installation of gcc3.3.3 doesn't have the bug. i've experimented extensively with a standalone executable and can't recreate the bug. i realize that the official release of gcc3.3.3 shipped with that bug so i assume that the build of gcc3.3.3 that i've acquired was patched.
so i think the problem relates to Calc in some way. how do i investigate this further? i'm thinking of rebuilding office from source so that i can debug, are there less drastic things i should try first?
many thanks eric
_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
