| You are not logged in. Login Now | register | search | ||||||||||||||||||
|
| |||
| Author | Message | ||
| 25 new of 260 responses total. | |||
|
aruba |
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 |
This response has been erased.
| ||
|
jep |
Why was Grex down for the last day or two? | ||
|
cross |
This response has been erased.
| ||
|
cross |
This response has been erased.
| ||
|
bhoward |
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 |
Is this a bug? | ||
|
aruba |
This response has been erased.
| ||
|
aruba |
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 |
_ _
_ _ _ __ | |_ _ ___| | ___ _
| | | | '_ \| | | | |/ __| |/ / | | |
| |_| | | | | | |_| | (__| <| |_| |
\__,_|_| |_|_|\__,_|\___|_|\_\\__, |
|___/
| ||
|
cross |
This response has been erased.
| ||
|
cross |
This response has been erased.
| ||
|
cross |
This response has been erased.
| ||
|
cross |
This response has been erased.
| ||
|
naftee |
fronttalk is hell. | ||
|
cross |
This response has been erased.
| ||
|
aruba |
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 |
This response has been erased.
| ||
|
keesan |
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 |
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 |
(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". | ||
|
keesan |
I am setting my terminal in .cshrc with /usr/bin/tset, which exists. I probably dialed in with linux on previous occasions and when I was asked about whether my terminal is [VT100] I typed linux. If I type linux or vt100 things work, the problem was when I hit the enter key for the default vt100 and it was interpreted as 'tset' being my terminal. I can try ssh'ing with DOS and hitting the Enter key some time. Maybe nobody else who dials in with DOS also accesses grex with linux and set it up this way. | ||
|
cross |
This response has been erased.
| ||
|
aruba |
Re #21: I care more about clarity than speed most of the time, too. But if you pick one library of classes and call it "standard", you can't get away form the fact that other people have different libraries that are more standard to them than yours. So what's clear to you won't be to them. If you have to drag a lot of libraries along with you whenever you port something to someplace new, that's a drawback in my book. Sometimes it's worth it, sometimes it's not. | ||
|
keesan |
Re 26, sometimes I telnet to grex after dialing with DOS. Why 'dialup?vt100' ? Sometimes I dial with linux, or ssh with linux. | ||
|
Response Not Possible: You are Not Logged In |
- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss