| Grex > Agora56 > #4: Grex System Problems - Winter 2005/06 |
| Grex System Problems - Winter 2005/06 | 
Dec 23 04:28 UTC 2005 |
This item is for system problems. If something on Grex isn't working right (line noise on a modem, weird behavior from a program, etc.), this is the place to announce it. Except for security holes. If you find a hole in system security, mail information about it to "staff".
| response 1 of 260: |
Dec 23 04:58 UTC 2005 |
A lot of things have been fixed, tuned or otherwise corrected in the weeks since the upgrade. Now might be a good time to look around and see what other systems issues are still outstanding -- broken or not working the same as before the upgrade -- and mention it here to make certain nothing gets overlooked.
| response 2 of 260: |
Dec 23 05:23 UTC 2005 |
I still can't compile my C++ programs since the upgrade. I compile the source files like this: g++ -c -fno-exceptions box.cpp g++ -c -fno-exceptions line.cpp g++ -c -fno-exceptions parse.cpp g++ -c -fno-exceptions token.cpp and then link them like this: ld -L/usr/lib/gcc-lib/i386-unknown-openbsd3.8/3.3.5 -lc -lm -lstdc++ -o box box.o line.o parse.o token.o The compiles go fine, but the linker has lots of errors of the form: /usr/lib/libstdc++.so.40.0: undefined reference to `_Unwind_Resume' /usr/lib/libstdc++.so.40.0: undefined reference to `_Unwind_DeleteException' and lots more like that. I'm not calling the "Unwind" routines from my code, so I presume the compiler is putting references in automatically. I thought maybe if I turned off exceptions that would take care of it, but as you can see the "-fno-exceptions" flag didn't fix the problem. So I need to either a) tell the compiler not to insert those references, or b) find the libraries that include those Unwind routines and link them in. Anybody have any ideas?
| response 3 of 260: |
Dec 23 06:18 UTC 2005 |
Try adding -lgcc and see if that fixes it.
| response 4 of 260: |
Dec 24 21:05 UTC 2005 |
THanks Mike - that's better. Now I only get two linker errors: /usr/lib/libc.so.38.2: undefined reference to `environ' /usr/lib/libc.so.38.2: undefined reference to `__progname' I'm not referring to those two variables in my program; it looks like libc is. Is that the right libc to use? Anybody know what library has those symbols?
| response 5 of 260: |
Dec 25 00:26 UTC 2005 |
This response has been erased.
| response 6 of 260: |
Dec 25 02:55 UTC 2005 |
Why was Grex down for the last day or two?
| response 7 of 260: |
Dec 25 04:29 UTC 2005 |
This response has been erased.
| response 8 of 260: |
Dec 25 05:17 UTC 2005 |
This response has been erased.
| response 9 of 260: |
Dec 25 06:55 UTC 2005 |
Happily, we're not getting the variety of crashes we used to see before the system upgrade and swapping out that memory. We appear to be down to just this one particular panic in softdep_write_inodeblock: panic: softdep_write_inodeblock: indirect pointer #0 mismatch 0 != 0 Starting stack trace... panic(d6a33880,d6a33880,e88e9d5c,e88e9db4,d6703b00) at panic+0x71 panic(d050a940,d0509dd7,0,0,0) at panic+0x71 initiate_write_inodeblock(e9be68dc,d6a68d58,d0f93000,0,e88e9e0c) at initiate_write_inodeblock+0x3c1 softdep_disk_io_initiation(d6a68d58,7fffffff,e88e9e5c,d021ae58) at softdep_disk_io_initiation+0x66 spec_strategy(e88e9e64,d6a13bb0,e88e9e6c,d067a2f4,0) at spec_strategy+0x42 spec_vnoperate(e88e9e64,40,e88e9e7c,80,d0580b80) at spec_vnoperate+0x16 VOP_STRATEGY(d6a68d58,d6a13e34,e88e9ebc,d02eed92,d6a13e34) at VOP_STRATEGY+0x25 bwrite(d6a68d58,d6a4f4a0,1,0,d6a13dc4) at bwrite+0xac spec_vnoperate(e88e9ed4,1,0,d6a68d58,d0580bc0) at spec_vnoperate+0x16 VOP_BWRITE(d6a68d58,0,1,0) at VOP_BWRITE+0x25 ffs_fsync(e88e9f24,d6a13dc4,10052,d6a27004,d05806c0) at ffs_fsync+0x1df VOP_FSYNC(d6a13dc4,d6a36000,3,d6a27004,0,12,d6a27004) at VOP_FSYNC+0x34 sched_sync(d6a27004) at sched_sync+0x100 Bad frame pointer: 0xd06f1ed8 End of stack trace. syncing disks...
| response 10 of 260: |
Dec 25 07:25 UTC 2005 |
Is this a bug?
| response 11 of 260: |
Dec 25 08:07 UTC 2005 |
This response has been erased.
| response 12 of 260: |
Dec 25 08:20 UTC 2005 |
Thanks Dan -
/--------------------------------\
| Now I can put things in boxes! |
\--------------------------------/
___ _ I can also use drop capitals, in any figlet font. Of
/ _ \ | | course, that necessitates writing a long paragraph,
/ /_\ \_ __ __| | which gets tiredome for the reader. I am curious what
| _ | '_ \ / _` | the correct libraries are to use with ld - Dan told me
| | | | | | | (_| | to use "c++" for both compiling and linking, and I
\_| |_/_| |_|\__,_| presume c++ is just g++ with certain options. (But
since it's a binary, I can't tell what options.) Still,
ln ought to work with the right libraries, oughtn't it?
___ _ how do I tell the linker not to give warnings whehever
/ _ \| | I use strcpy or sprintf? It seems very maternalistic
/ /_\ \ |___ ___ about that. There must be some option that turns off
| _ | / __|/ _ \ those warnings, I would think.
| | | | \__ \ (_) |
\_| |_/_|___/\___( )
|/