David Leimbach wrote:
I think C takes a more low-level approach and says "void * is just an address
void * + 1 means the next valid address".
This is not true.
The ANSI C standard forbids arithmetic on void * pointers,
just as C++ does.
GNU gcc has supported void * arithmetic for a long
time as an
I always feel better when I convert void * to char * but that's probably
because C++ doesn't allow pointer arithmetic on void *'s. The argument
being that you don't know the size of what's being pointed to with a void *
and therefore can't know how far to seek the the pointer to get to the next
On Thu, Jul 10, 2003 at 03:42:04AM -0700, Terry Lambert wrote:
> Luigi Rizzo wrote:
> > in several places in ipfw2.c i have to move pointers across
> > structures of variable length (lists of ipfw2 instructions
> > returned by the getsockopt()), and i use the following type of code:
> >
> >
ext = (void *)p + len;
> foo = (foo *)p + len;
>
> When using WARNS=5, the compiler in -current flags them with 'Warning
> void * arithmetic'.
>
> What is the best way to do the above given that i do need to use
> these variable-size structures ?
I don't under
R> foo *p;
LR>
LR> ...
LR>
LR> next = (void *)p + len;
LR> ...
LR> foo = (foo *)p + len;
LR>
LR>When using WARNS=5, the compiler in -current flags them with 'Warning
LR>void * arithmetic'.
LR>
LR>What is the best way to do the
;
...
foo = (foo *)p + len;
When using WARNS=5, the compiler in -current flags them with 'Warning
void * arithmetic'.
What is the best way to do the above given that i do need to use
these variable-size structures ?
cheers
luigi
I just got a panic. As I have never had one before, I don't know what to
do. It's on another system so I don't have to reboot immediately (that
would solve the problem temporarily, wouldn't it?) if someone would give
me some advice, I could try to help debug it; however,
On Fri, Mar 28, 2003 at 12:54:16AM -0500, taxman wrote:
> that gives an error that is similiar to:
> WARNING: syntax error on file /boot/loader.conf
> dumpdev=/dev/ad0s1b
> ^
Hi Tim,
Please do 'dumpdev="/dev/ad0s1b". The doube quotes is a must .
Jiawei
--
"Without the userland, th
On Wednesday 26 March 2003 07:54 pm, Greg 'groggy' Lehey wrote:
> On Wednesday, 26 March 2003 at 13:35:28 +, Jason Morgan wrote:
> > I just got a panic. As I have never had one before, I don't know what to
> > do. It's on another system so I don't ha
On Thu, Mar 27, 2003 at 11:24:44AM +1030, Greg 'groggy' Lehey wrote:
> On Wednesday, 26 March 2003 at 13:35:28 +, Jason Morgan wrote:
> > I just got a panic. As I have never had one before, I don't know what to
> > do. It's on another system so I don
On Wednesday, 26 March 2003 at 13:35:28 +, Jason Morgan wrote:
> I just got a panic. As I have never had one before, I don't know what to
> do. It's on another system so I don't have to reboot immediately (that
> would solve the problem temporarily, wouldn't it
On Wed, Mar 26, 2003 at 07:49:40PM +0100, Simon L. Nielsen wrote:
> On 2003.03.26 13:35:28 +, Jason Morgan wrote:
>
> > I just got a panic. As I have never had one before, I don't know what to
> > do. It's on another system so I don't have to reboot immediate
On 2003.03.26 13:35:28 +, Jason Morgan wrote:
> I just got a panic. As I have never had one before, I don't know what to
> do. It's on another system so I don't have to reboot immediately (that
Have a look at
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/advan
I just got a panic. As I have never had one before, I don't know what to
do. It's on another system so I don't have to reboot immediately (that
would solve the problem temporarily, wouldn't it?) if someone would give
me some advice, I could try to help debug it; however,
Dear Hackers,
Does anyone know what is the proper handling for USB IOERROR status
in USB transfer callback?
here is my problem. the driver opens bulk pipe and submits incoming
USB bulk transfer. the USB device is detached while the transfer is
still pending and pipe is still open. USB transfer
In article you write:
>From my observations (yes, please correct me if I am wrong), that
>modules define what to support in their respective makefiles in the form
>of
>
>SRC= aaa.c bbb.c opt_*.h
>
>Where opt_*.h are automagically generated if they are not in machine@
>(and
>From my observations (yes, please correct me if I am wrong), that modules define what
>to support in their respective makefiles in the form of
SRC= aaa.c bbb.c opt_*.h
Where opt_*.h are automagically generated if they are not in machine@ (and the
generated files are just empty file
On Mon, 2003/02/24 at 17:28:57 -0500, Daniel Eischen wrote:
> So I got a new Dell laptop, ATI Radeon 7500. Installed FreeBSD
> 5.0-RELEASE, X 4.2.1, and KDE right off the FreeBSD Mall CD-ROM.
> I configured X from the installation setup and was happily
> running X and KDE @ 1400x1050. Cool.
>
>
So I got a new Dell laptop, ATI Radeon 7500. Installed FreeBSD
5.0-RELEASE, X 4.2.1, and KDE right off the FreeBSD Mall CD-ROM.
I configured X from the installation setup and was happily
running X and KDE @ 1400x1050. Cool.
Then I cvsup'd to a recent -current from about a week ago,
which my othe
Maybe anyone will enlighten me:
I am working with the port lang/gnat (Ada compiler)
and it links with nonexistent libaddr2line
(symbol convert_addresses) to find the line numbers
from executables.
Where to look for the correct way to resolve addresses
to line numbers in FreeBSD ?
Thanx,
Yuri.
T
What is the use of
options FB_INSTALL_CDEV # install a CDEV entry in /dev
for in 5-CURRENT?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, 4 Feb 2003, Ilmar S. Habibulin wrote:
> On Mon, 3 Feb 2003, Robert Watson wrote:
>
> > The strategy for selecting a credential to check against is generally to
> > use td_ucred, and to hold no locks. You'll see that suser() does this,
> > for example. Under some circumstances: specific
On Mon, 3 Feb 2003, Robert Watson wrote:
> The strategy for selecting a credential to check against is generally to
> use td_ucred, and to hold no locks. You'll see that suser() does this,
> for example. Under some circumstances: specifically, credential updates,
> you need to hold the process
On Mon, 3 Feb 2003, Ilmar S. Habibulin wrote:
> Why not to use only credits for proc and make td_ucred macro like
> td_proc->p_ucred? Or it has some meaning that i do not understand?
td_ucred is a cached copy of p_ucred. The cached copy is potentially
updated on any entry to the kernel. The re
Apparently, On Mon, Feb 03, 2003 at 09:08:41AM -0500,
Ilmar S. Habibulin said words to the effect of;
>
> Why not to use only credits for proc and make td_ucred macro like
> td_proc->p_ucred? Or it has some meaning that i do not understand?
td_ucred is a read only reference to p_ucred, s
Why not to use only credits for proc and make td_ucred macro like
td_proc->p_ucred? Or it has some meaning that i do not understand?
Thank you for help.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
rence), uid 1001: exited
> on signal 11 (core dumped)
>
> what the heck is this?
An xscreensaver hack. It dumps core for me a lot too, I haven't
figured out why.
Kris
msg49415/pgp0.pgp
Description: PGP signature
Brandon S. Allbery KF8NH wrote:
On Sun, 2002-12-29 at 19:06, redjupiter wrote:
pid 2612 (interference), uid 1001: exited on signal 11 (core dumped)
Dec 29 22:40:09 byblos kernel: pid 2612 (interference), uid 1001: exited
on signal 11 (core dumped)
what the heck is this?
Most probably
On Sun, 2002-12-29 at 19:06, redjupiter wrote:
> pid 2612 (interference), uid 1001: exited on signal 11 (core dumped)
> Dec 29 22:40:09 byblos kernel: pid 2612 (interference), uid 1001: exited
> on signal 11 (core dumped)
>
> what the heck is this?
Most probably it's
-r-xr
HI guys,
Hope someone is awake :-)
watching my dmesg I saw the following:
pid 2612 (interference), uid 1001: exited on signal 11 (core dumped)
Dec 29 22:40:09 byblos kernel: pid 2612 (interference), uid 1001: exited
on signal 11 (core dumped)
what the heck is this?
I am using RC1 and
On Fri, Dec 06, 2002 at 05:10:11PM -0500, Paul Murphy wrote:
> On Fri, 6 Dec 2002 14:29:37 -0700
> "Cliff L. Biffle" <[EMAIL PROTECTED]> wrote:
>
>
> > group know that the world and kernel seem quite stable using the athlon-tbird
> > optimizations. Not to mention smokingly fast.
>
> Is that j
On Fri, 6 Dec 2002 14:29:37 -0700
"Cliff L. Biffle" <[EMAIL PROTECTED]> wrote:
> group know that the world and kernel seem quite stable using the athlon-tbird
> optimizations. Not to mention smokingly fast.
Is that just a -CURRENT thing, I can't see anything like that in -STABLE's LINT.
--
On Fri, 06 Dec 2002, Cliff L. Biffle wrote:
> On Friday 06 December 2002 01:11 pm, leafy wrote:
> > CPUTYPE=pentium4 is know to be broken. What is the known working highest
> > CPUTYPE then? pentium3 or pentium2?
>
> Well, I know this isn't quite what you were askin
On Friday 06 December 2002 01:11 pm, leafy wrote:
> CPUTYPE=pentium4 is know to be broken. What is the known working highest
> CPUTYPE then? pentium3 or pentium2?
Well, I know this isn't quite what you were asking, but I wanted to let the
group know that the world and kernel seem q
In the last episode (Dec 07), leafy said:
> Hi,
>
> CPUTYPE=pentium4 is know to be broken. What is the known working highest
> CPUTYPE then? pentium3 or pentium2?
p3 has been working for me for quite a while.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send ma
Hi,
CPUTYPE=pentium4 is know to be broken. What is the known working highest
CPUTYPE then? pentium3 or pentium2?
JY
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sun, 17-Nov-2002 at 17:20:56 -0500, John De Boskey wrote:
> In trying to setup a ccd on a -current system I
> seem to have run into a few issues:
>
> /etc/ccd.conf:
> # ccd ileave flags component devices
> ccd0 64 none/dev/ad1s1a /dev/ad2s1a
>
> # ccdconfig -g
> In trying to setup a ccd on a -current system I
> seem to have run into a few issues:
>
> /etc/ccd.conf:
> # ccd ileave flags component devices
> ccd0 64 none/dev/ad1s1a /dev/ad2s1a
>
> # ccdconfig -g
> ccd064 0 /dev/ad1s1a /dev/ad2s1a
>
In trying to setup a ccd on a -current system I
seem to have run into a few issues:
/etc/ccd.conf:
# ccd ileave flags component devices
ccd0 64 none/dev/ad1s1a /dev/ad2s1a
# ccdconfig -g
ccd064 0 /dev/ad1s1a /dev/ad2s1a
# ls -al /dev/ccd*
In message: <[EMAIL PROTECTED]>
David Gilbert <[EMAIL PROTECTED]> writes:
: > "M" == M Warner Losh <[EMAIL PROTECTED]> writes:
:
: M> In message: <[EMAIL PROTECTED]> Ceri Davies
: M> <[EMAIL PROTECTED]> writes: : For that matter, do we still
: M> need xten, a user who has been push
> "M" == M Warner Losh <[EMAIL PROTECTED]> writes:
M> In message: <[EMAIL PROTECTED]> Ceri Davies
M> <[EMAIL PROTECTED]> writes: : For that matter, do we still
M> need xten, a user who has been pushed so far : to the edge of
M> obscurity that it's home directory doesn't even exist on a :
M> fr
On Wed, Nov 06, 2002 at 05:57:22PM -0700, Lyndon Nerenberg wrote:
> >> Maybe future generations will wonder what it is named after
> >> similarly to GCOS field in passwd today :-)
> >
> >At the very least we should change the shell. But Kris' suggestions
> &
>> Maybe future generations will wonder what it is named after
>> similarly to GCOS field in passwd today :-)
>
>At the very least we should change the shell. But Kris' suggestions
>sound the best.
I agree. But more importantly, let's make sure that we don't,
the serial port devices (which are owned by the uucp user). Really,
>> the uucp user is now misnamed and should be called something like
>
> Let's leave it like it is.
>
> Maybe future generations will wonder what it is named after
> similarly to GCOS field in passwd toda
On Wed, Nov 06, 2002 at 04:23:38AM -0700, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Ceri Davies <[EMAIL PROTECTED]> writes:
> : For that matter, do we still need xten, a user who has been pushed so far
> : to the edge of obscurity that it's home directory doesn't even ex
In message: <[EMAIL PROTECTED]>
Ceri Davies <[EMAIL PROTECTED]> writes:
: For that matter, do we still need xten, a user who has been pushed so far
: to the edge of obscurity that it's home directory doesn't even exist on a
: freshly installed system (and I'm not talking about /nonexist
serial port devices (which are owned by the uucp user). Really,
> > the uucp user is now misnamed and should be called something like
>
> Let's leave it like it is.
>
> Maybe future generations will wonder what it is named after
> similarly to GCOS field in passwd toda
er is now misnamed and should be called something like
Let's leave it like it is.
Maybe future generations will wonder what it is named after
similarly to GCOS field in passwd today :-)
--
<< Marcin Cieslak // [EMAIL PROTECTED] >>
msg46137/pgp0.pgp
Description: PGP signature
On Sat, Nov 02, 2002 at 04:11:39PM +1030, Greg 'groggy' Lehey wrote:
> Now that uucp is no longer in the base system, is there any reason to
> keep user uucp in /usr/src/etc/master.passwd?
A number of base system utilities and ports still use it for access to
the serial port devices (which are own
On Sat, Nov 02, 2002 at 01:01:34PM +0200, John Hay wrote:
> > > Now that uucp is no longer in the base system, is there any reason to
> > > keep user uucp in /usr/src/etc/master.passwd?
> >
> > Probably not. If you remove this, please coordinate an upgrade
> > to the net/freebsd-uucp port the get
John Hay wrote:
> > > Now that uucp is no longer in the base system, is there any reason to
> > > keep user uucp in /usr/src/etc/master.passwd?
> >
> > Probably not. If you remove this, please coordinate an upgrade
> > to the net/freebsd-uucp port the get the user added there.
>
> Also remember t
> > Now that uucp is no longer in the base system, is there any reason to
> > keep user uucp in /usr/src/etc/master.passwd?
>
> Probably not. If you remove this, please coordinate an upgrade
> to the net/freebsd-uucp port the get the user added there.
Also remember that /dev/cua* is owned by uucp
> Now that uucp is no longer in the base system, is there any reason to
> keep user uucp in /usr/src/etc/master.passwd?
Probably not. If you remove this, please coordinate an upgrade
to the net/freebsd-uucp port the get the user added there.
Thanks!
M
--
o Mark Murray
\_
O.\_Warning:
Now that uucp is no longer in the base system, is there any reason to
keep user uucp in /usr/src/etc/master.passwd?
Greg
--
See complete headers for address and phone numbers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Mon, 19 Aug 2002 16:29:36 +0200 Radko Keves wrote:
> Security Advisory FreeBSD-SA-02:38.signed-error
[patch output]
> i know that patch wasn't for current, but is it needed to patch it ?
no. -current is the development branch and thus there are virtually
never advisories. -current is risky an
Security Advisory FreeBSD-SA-02:38.signed-error
i try to patch it (of cource in current ;( ) and:
The text leading up to this was:
--
|Index: sys/i386/isa/vesa.c
|diff -u sys/i386/isa/vesa.c:1.32 sys/i386/isa/vesa.c:1.32.10.1
|--- sys/i386/isa/vesa.c:1.32 Sat Jan 29 07:
Christian Weisgerber <[EMAIL PROTECTED]> wrote:
> -CURRENT/alpha as of 1..2 days ago. I can load my sound modules
> just fine but they don't show up in the kernel messages, and the
> corresponding devices under /dev don't exist.
Must have been a fluke. Everything is back after a reboot.
(The r
-CURRENT/alpha as of 1..2 days ago. I can load my sound modules
just fine
# kldstat
...
223 0xfe00031aa000 3snd_pcm.ko
232 0xfe00031da000 16000snd_sbc.ko
241 0xfe00031f 16000snd_sb16.ko
but they don't show up in the kernel messages, and the correspond
On Tue, Jul 16, 2002 at 07:14:05PM -0400, John Baldwin wrote:
>
> This is because USB network drivers are possibly doing bad things. Either
> that or the network locking is making bogus assumptions about what
> device driver routines will and will not do. Probably the network st
at the moment?
This is because USB network drivers are possibly doing bad things. Either
that or the network locking is making bogus assumptions about what
device driver routines will and will not do. Probably the network stack
should not hold locks across a driver's start method.
--
On Thu, Jul 11, 2002 at 12:33:27PM +0100, Josef Karthauser wrote:
> On Thu, Jul 11, 2002 at 04:01:08AM -0700, Don Lewis wrote:
[stuff about
could sleep with "inp" locked from /usr/src/sys/netinet/tcp_usrreq.c:647
could sleep with "tcp" locked from /usr/src/sys/netinet/tcp_usrreq.c:630
cut
er ten seconds ...
>
> I'm seeing this:
>
> ../../../vm/uma_core.c:1332: could sleep with "kernel linker" locked from
>../../../kern/kern_linker.c:1797
>
> very early on (before rc.sysctl is read -- okay I'm still using the old rc
> scripts).
I see that
On Fri, Jul 12, 2002 at 08:33:39 -0700, Alex Zepeda wrote:
> On Wed, Jul 10, 2002 at 01:36:46PM -0700, Don Lewis wrote:
>
> > It'll drop into ddb every time you get a witness error and you'll have
> > to tell ddb to continue. This could be a might annoying if you are
> > getting errors ever ten
On Wed, Jul 10, 2002 at 01:36:46PM -0700, Don Lewis wrote:
> It'll drop into ddb every time you get a witness error and you'll have
> to tell ddb to continue. This could be a might annoying if you are
> getting errors ever ten seconds ...
I'm seeing this:
../../../vm/uma_core.c:1332: could sle
On 11 Jul, Don Lewis wrote:
> On 10 Jul, Alex Zepeda wrote:
>> On Wed, Jul 10, 2002 at 01:34:50PM -0700, Don Lewis wrote:
>>
>>> > ../../../vm/uma_core.c:1332: could sleep with "inp" locked from
>../../../netinet/tcp_subr.c:935
>>> > ../../../vm/uma_core.c:1332: could sleep with "tcp" locked fro
On 11 Jul, Josef Karthauser wrote:
> On Thu, Jul 11, 2002 at 04:01:08AM -0700, Don Lewis wrote:
>> On 11 Jul, Josef Karthauser wrote:
>> >> I get it whenever cron kicks of a cvsup also.
>> The cvsup server may also be making ident queries.
>
> If it is, it is making lots and lots of them, at a
On Thu, Jul 11, 2002 at 04:01:08AM -0700, Don Lewis wrote:
> On 11 Jul, Josef Karthauser wrote:
> > On Thu, Jul 11, 2002 at 11:35:46AM +0100, Josef Karthauser wrote:
> >>
> >> > I tracked it down to tcp_getcred() calling SYSCTL_OUT(), which can
> >> > potentially block, before releasing the locks
On 11 Jul, Josef Karthauser wrote:
> On Thu, Jul 11, 2002 at 11:35:46AM +0100, Josef Karthauser wrote:
>>
>> > I tracked it down to tcp_getcred() calling SYSCTL_OUT(), which can
>> > potentially block, before releasing the locks tcp_getcred() is holding.
>> > This routine is used by the net.inet.
On Thu, Jul 11, 2002 at 11:35:46AM +0100, Josef Karthauser wrote:
>
> > I tracked it down to tcp_getcred() calling SYSCTL_OUT(), which can
> > potentially block, before releasing the locks tcp_getcred() is holding.
> > This routine is used by the net.inet.tcp.getcred sysctl, and the only
> > user
On Thu, Jul 11, 2002 at 03:12:34AM -0700, Don Lewis wrote:
> >>
> >> I've never seen that one. I'll take a look at the code, though.
> >
> > I'm seeing the same (once at bootup tho).
> >
> > sm:blarf:~$uptime
> > 8:48PM up 18:52, 4 users, load averages: 0.11, 0.06, 0.01
> > sm:blarf:~$
>
>
On 10 Jul, Alex Zepeda wrote:
> On Wed, Jul 10, 2002 at 01:34:50PM -0700, Don Lewis wrote:
>
>> > ../../../vm/uma_core.c:1332: could sleep with "inp" locked from
>../../../netinet/tcp_subr.c:935
>> > ../../../vm/uma_core.c:1332: could sleep with "tcp" locked from
>../../../netinet/tcp_subr.c:92
On Wed, Jul 10, 2002 at 01:34:50PM -0700, Don Lewis wrote:
> > ../../../vm/uma_core.c:1332: could sleep with "inp" locked from
>../../../netinet/tcp_subr.c:935
> > ../../../vm/uma_core.c:1332: could sleep with "tcp" locked from
>../../../netinet/tcp_subr.c:928
>
> I've never seen that one. I'
On 10 Jul, Alex Zepeda wrote:
> On Wed, Jul 10, 2002 at 02:43:54AM -0700, Don Lewis wrote:
>
>> I haven't had any instability problems in a while on my UP box.
>
> Seems like the UP kernels are more unstable for me. Go figure.
>
>> > ../../../vm/uma_core.c:1332: could sleep with "process lock"
On 10 Jul, Dan Nelson wrote:
> I see this one once every 10 seconds or so:
>
> ../../../vm/uma_core.c:1332: could sleep with "inp" locked from
>../../../netinet/tcp_subr.c:935
> ../../../vm/uma_core.c:1332: could sleep with "tcp" locked from
>../../../netinet/tcp_subr.c:928
I've never seen th
Dag-Erling Smorgrav wrote:
> Alex Zepeda <[EMAIL PROTECTED]> writes:
> > After the rude awakening that I was after all running current, I've
> > finally turned on the WITNESS related options for my kernel
>
> Congratulations in turning your -CURRENT box into a doorstop! ;)
Magician: For m
On Wed, Jul 10, 2002 at 02:43:54AM -0700, Don Lewis wrote:
> I haven't had any instability problems in a while on my UP box.
Seems like the UP kernels are more unstable for me. Go figure.
> > ../../../vm/uma_core.c:1332: could sleep with "process lock" locked from
>../../../kern/kern_exec.c:3
In the last episode (Jul 10), Don Lewis said:
> On 10 Jul, Alex Zepeda wrote> After the rude awakening that I was after all running
>current, I've
> > finally turned on the WITNESS related options for my kernel (and boy is it
> > wickedly unstable as of now).
>
> I haven't had any instability pr
Alex Zepeda <[EMAIL PROTECTED]> writes:
> After the rude awakening that I was after all running current, I've
> finally turned on the WITNESS related options for my kernel
Congratulations in turning your -CURRENT box into a doorstop! ;)
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubs
On 10 Jul, Alex Zepeda wrote> After the rude awakening that I was after all running
current, I've
> finally turned on the WITNESS related options for my kernel (and boy is it
> wickedly unstable as of now).
I haven't had any instability problems in a while on my UP box.
> Anyways.. is there any
After the rude awakening that I was after all running current, I've
finally turned on the WITNESS related options for my kernel (and boy is it
wickedly unstable as of now). Anyways.. is there any sort of list of
known warnings? I'm seeing a few consistantly relating to "pcm0:play:0",
"pcm0", "i
"David O'Brien" <[EMAIL PROTECTED]> wrote:
> I can rlogin to a -CURRENT box as root. However `rsh box id' comes back
> with:
>
> Jul 3 00:11:33 box rshd[4916]: root@dragon as rootk: permission denied
> (authentication error). cmd='id'
man pam_rhosts should explain that.
--
cheers, J
I can rlogin to a -CURRENT box as root. However `rsh box id' comes back
with:
Jul 3 00:11:33 box rshd[4916]: root@dragon as rootk: permission denied
(authentication error). cmd='id'
Is PAM getting in the way here or something?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsu
no I didn't apply it but Tor just found the problem in the pmap
code.
On Wed, 26 Jun 2002, walt wrote:
> Julian Elischer wrote to FreeBSD-Current:
>
> > /usr/libexec/ld-elf.so.1: grep: Shared object has no run-time symbol
> > table
>
> This is the same disaster that struck me yesterday aft
[EMAIL PROTECTED] wrote:
> >
> > sure enough:
> > ref4# grep
> > /usr/libexec/ld-elf.so.1: grep: Shared object has no run-time symbol table
> > ref4#
> >
> >
> > huh?
> >
> > freshly cvsup'd sources..
>
>
> Too many pages were prefaulted in pmap_object_init_pt, thus the wrong
> physical pag
> Just to make it absolutely clear, however: did you also apply
> Alexander's patch before seeing this error?
No, the problem was unrelated.
> I finally gave up and did a binary-only reinstall from a -CURRENT
> "Preview" snapshot which fixed everything. I'm going to sit and
> watch for awhile
Julian Elischer wrote to FreeBSD-Current:
> /usr/libexec/ld-elf.so.1: grep: Shared object has no run-time symbol
> table
This is the same disaster that struck me yesterday after I applied
Alexander's C++ patch and I initially thought it was due to that.
Just to make it absolutely clear, howev
>
> sure enough:
> ref4# grep
> /usr/libexec/ld-elf.so.1: grep: Shared object has no run-time symbol table
> ref4#
>
>
> huh?
>
> freshly cvsup'd sources..
Too many pages were prefaulted in pmap_object_init_pt, thus the wrong
physical page was entered in the pmap for the virtual address whe
I will add that the file is not really corrupt..
A reboot brings it 'back to life' so it's only corrupt in memory.
On Wed, 26 Jun 2002, Julian Elischer wrote:
>
> After doing a make buildworld,
> followed by make installworld and mergemaster.
>
> The following 'make buildworld' starts of wit
After doing a make buildworld,
followed by make installworld and mergemaster.
The following 'make buildworld' starts of with:
ref4# make buildworld
/usr/libexec/ld-elf.so.1: grep: Shared object has no run-time symbol table
--
>>> Rebui
On Fri, Jun 07, 2002 at 02:44:41AM +0200, Martin Blapp wrote:
> What is the status here ? In my CURRENT system, these compat
> libs are still the old ones :-(
>
> I've now updated the libs manually to be able to run OO
> on CURRENT. And yes - it works. Yes :-))
I don't
Hi Terry,
> I saw a posting of some of the breakage. There was a type that
> wasn't defined in scope in a prototype, and then there were a
> couple that were missing (e.g. "unexpected ;") because of some
> bogus includes. I didn't really see anything that I could blame
> on GCC31 itself (I adm
Martin Blapp wrote:
> > I also think that it may mean another major version number change,
> > since there's aren't real minor version numbers any more. 8-(.
>
> That surly not necessary. We only have major version number change
> if we change from Releng Majors 3->4, 4->5. This is just compat
>
Hi
> I think that if this is going to result in MFC's of things that
> change the libraries for 4.6, that the update of the libc image
> in 5.x for -compat is going to have to wait for 4.6-RELEASE.
That's a good idea.
> I also think that it may mean another major version number change,
> since
Martin Blapp wrote:
> > Why is it linked against a hacked 4.x libc, instead of an
> > unhacked 5.x libc?
>
> Because gcc31 and libstd++ and stlport are unusable for OpenOffice
> to build. Exceptions are broken. Optimazations are broken.
I think that if this is going to result in MFC's of things
Hi,
> Why is it linked against a hacked 4.x libc, instead of an
> unhacked 5.x libc?
Because gcc31 and libstd++ and stlport are unusable for OpenOffice
to build. Exceptions are broken. Optimazations are broken.
>
> Why is the compat stuff necessary for -current at all?
Because some users like
Martin Blapp wrote:
> What is the status here ? In my CURRENT system, these compat
> libs are still the old ones :-(
>
> I've now updated the libs manually to be able to run OO
> on CURRENT. And yes - it works. Yes :-))
>
> -r--r--r-- 1 root wheel 725012 Jun 7
Hi,
What is the status here ? In my CURRENT system, these compat
libs are still the old ones :-(
I've now updated the libs manually to be able to run OO
on CURRENT. And yes - it works. Yes :-))
-r--r--r-- 1 root wheel 725012 Jun 7 02:36 libc.so.4
-r--r--r-- 1 root wheel 675600 J
I get this semi-randomly on my laptop when doing a delete ... softupdates
are enabled on the file system in question, and am running -CURRENT as of
last night, if any of that matters?
===> Cleaning for XFree86-font75dpi-4.2.0
rm: fts_read: No such file or directory
*** Error code 1
To Unsub
A GENERIC kernel on current fails to compile missing softintr.
#
beast:/sys/i386/compile/GENERIC # make -DNO_MODULES -DNO_WERROR
cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winlin
rob wrote:
> Pardon my ignorant question. What is Tinderbox? My guess is that its a
> special machine for doing some testing. Rob.
A tinderbox is a machine dedicated to building something big and
complex. Here's a good example from the mozilla project.
http://tinderbox.
401 - 500 of 610 matches
Mail list logo
