You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   175-199   200-224 
 225-249   250-260         
 
Author Message
i
Grex System Problems - Winter 2005/06 Mark Unseen   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".
260 responses total.
bhoward
response 1 of 260: Mark Unseen   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.
aruba
response 2 of 260: Mark Unseen   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?
mcnally
response 3 of 260: Mark Unseen   Dec 23 06:18 UTC 2005

  Try adding -lgcc and see if that fixes it.
aruba
response 4 of 260: Mark Unseen   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?
cross
response 5 of 260: Mark Unseen   Dec 25 00:26 UTC 2005

This response has been erased.

jep
response 6 of 260: Mark Unseen   Dec 25 02:55 UTC 2005

Why was Grex down for the last day or two?
cross
response 7 of 260: Mark Unseen   Dec 25 04:29 UTC 2005

This response has been erased.

cross
response 8 of 260: Mark Unseen   Dec 25 05:17 UTC 2005

This response has been erased.

bhoward
response 9 of 260: Mark Unseen   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... 
keesan
response 10 of 260: Mark Unseen   Dec 25 07:25 UTC 2005

Is this a bug?
aruba
response 11 of 260: Mark Unseen   Dec 25 08:07 UTC 2005

This response has been erased.

aruba
response 12 of 260: Mark Unseen   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.
| | | | \__ \ (_) |
\_| |_/_|___/\___( )
                 |/

naftee
response 13 of 260: Mark Unseen   Dec 25 14:29 UTC 2005

             _            _
 _   _ _ __ | |_   _  ___| | ___   _
| | | | '_ \| | | | |/ __| |/ / | | |
| |_| | | | | | |_| | (__|   <| |_| |
 \__,_|_| |_|_|\__,_|\___|_|\_\\__, |
                               |___/
cross
response 14 of 260: Mark Unseen   Dec 25 16:11 UTC 2005

This response has been erased.

cross
response 15 of 260: Mark Unseen   Dec 25 16:15 UTC 2005

This response has been erased.

cross
response 16 of 260: Mark Unseen   Dec 25 16:20 UTC 2005

This response has been erased.

cross
response 17 of 260: Mark Unseen   Dec 25 16:22 UTC 2005

This response has been erased.

naftee
response 18 of 260: Mark Unseen   Dec 25 18:48 UTC 2005

fronttalk is hell.
cross
response 19 of 260: Mark Unseen   Dec 25 20:13 UTC 2005

This response has been erased.

aruba
response 20 of 260: Mark Unseen   Dec 25 20:56 UTC 2005

Thanks Dan.  I know everyone has a string class they think is the answer to
all problems; I've written a few of them myself.  But a lot of times I don't
want or need the overhead.
cross
response 21 of 260: Mark Unseen   Dec 25 21:14 UTC 2005

This response has been erased.

keesan
response 22 of 260: Mark Unseen   Dec 26 01:15 UTC 2005

I just dialed into grex (with DOS kermit) and instead of letting me hit
Enter to select the default VT100:
Terminal type:  [vt100]  (I hit Enter key)
tset:  unknown terminal type
I had to type out VT100.
What was changed and please fix it.  I don't know how long ago this happened
because I was not able to dial in for a couple of weeks, maybe the BSD upgrade
caused the problem.
gelinas
response 23 of 260: Mark Unseen   Dec 26 02:48 UTC 2005

You dialed in for 30 minutes on December 22:

keesan    tty01                             Thu Dec 22 13:28 - 13:58  (00:29)

I don't think anything has changed since then. 
bhoward
response 24 of 260: Mark Unseen   Dec 26 05:55 UTC 2005

(Joe's comment slipped in ahead of mine)

Nothing has been changed since I fixed the dialup line tty speed a
week or so ago.

Is it possible that your .login or .profile has some dependency on
the default tty value used on the dialin lines?  The default TERM
for tty00 and tty01 is now "dialup" instead of "unknown".
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   175-199   200-224 
 225-249   250-260         
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss