Thread View: gnu.g++.lib.bug
1 messages
1 total messages
Started by Arne Henrik Juul
Sat, 12 Dec 1992 23:00
libg++ 2.3 fails on Ultrix 4.2A
Author: Arne Henrik Juul
Date: Sat, 12 Dec 1992 23:00
Date: Sat, 12 Dec 1992 23:00
68 lines
3405 bytes
3405 bytes
I'm trying to install libg++ 2.3 on Ultrix 4.2A (decstation), using
gcc 2.3.1. I get the following errors when doing make -k check in the
iostream/test directory:
munti:/local/src/libg++-2.3/libg++/iostream/test:(611)$ make -k check
./tFile < ./tFile.inp > tFile.out 2>&1
/bin/sh: 8880 Memory faultmake: *** [check-tFile-regular] Error 139
./tFile -b0 < ./tFile.inp > tFile-nobuf.out 2>&1
/bin/sh: 8883 Memory faultmake: *** [check-tFile-nobuf] Error 139
./tFile -b3 < ./tFile.inp > tFile-buf3.out 2>&1
/bin/sh: 8885 Memory faultmake: *** [check-tFile-buf3] Error 139
./hounddog <./hounddog.in > hounddog.out 2>&1
/bin/sh: 8887 Memory faultmake: *** [check-hounddog] Error 139
./putbackdog <./hounddog.in > putbackdog.out 2>&1
/bin/sh: 8889 Memory faultmake: *** [check-putbackdog-regular] Error 139
./putbackdog -b0 <./hounddog.in > putbackdog-nobuf.out 2>&1
/bin/sh: 8891 Memory faultmake: *** [check-putbackdog-nobuf] Error 139
./putbackdog -b2 <./hounddog.in > putbackdog-buf2.out 2>&1
/bin/sh: 8893 Memory faultmake: *** [check-putbackdog-buf2] Error 139
./tformat
Encountered no errors in make: *** [check-tformat] Segmentation fault
./tiformat
Encountered no errors in make: *** [check-tiformat] Segmentation fault
./tiomanip >tiomanip.out 2>&1
/bin/sh: 8897 Memory faultmake: *** [check-tiomanip] Error 139
make: Target `check' not remade because of errors.
In other words, things doesn't work at all.
I haven't got very far in debugging this yet, but this is the gdb
traceback from running tiomanip:
munti:/local/src/libg++-2.3/libg++/iostream/test:(614)$ gdb tiomanip core
GDB is free software and you are welcome to distribute copies of it
under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.7, Copyright 1992 Free Software Foundation, Inc...
Core was generated by `tiomanip'.
#0 0x404e84 in write_int (stream=0x10000aa0, val=void, neg=0)
at iostream.C:374
(gdb) where
#0 0x404e84 in write_int (stream=0x10000aa0, val=void, neg=0)
at iostream.C:374
#1 0x4051d8 in ostream::operator<< (this=0x10000aa0, n=1234) at iostream.C:426
#2 0x40021c in main () at tiomanip.C:91
(gdb) list
369 }
370 else { // Decimal
371 #ifdef __GNUC__
372 // Optimization: Only use long long when we need to.
373 while (val > UINT_MAX) {
374 *--buf_ptr = (val % 10) + '0';
375 val /= 10;
376 }
377 // Use more efficient (int) arithmetic for the rest.
378 register unsigned int ival = (unsigned int)val;
Should I try gcc 2.3.2, or should I wait for a bugfix release of
libg++ ? This isn't a big problem for me right now, as I have libg++
2.2 which works well for my (limited) needs. Do others see these
problems as well ?
--
Arne H. Juul -- arnej@lise.unit.no -- University of Trondheim, Norway
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads