On Mon, 11 Nov 2002, David Malone wrote:
DM>On Mon, Nov 11, 2002 at 04:52:22PM +0100, Harti Brandt wrote:
DM>AG>But does using a union make it safe?
DM>
DM>> Well, I just had a long discussion with a collegue about the topic. The
DM>> main problem is in the ISO-C standard, section 6.7 point 4 whic
Hi all,
In a dual boot situation, is it possible to be logged into -CURRENT and
build -STABLE ( ie -STABLE filesystems live on separate fdisk partitions
and are exported ) ?
Thanks
- aW
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the mess
Doug Rabson wrote:
> In the windows world, all this is handled by having a strict list of explicit
> symbol exports, either in the source code using syntax extensions or with a
> file supplied to the linker. I'm not sure whether binutils supports this kind
> of thing but it would allow us to cut
On Mon, 2002-11-11 at 20:39, Lucky Green wrote:
> Are there any potential draw backs to enabling DRM_LINUX? Or should
> DRM_LINUX be enabled whenever one enables COMPAT_LINUX?
>
> This has not been clear to me from reading NOTES.
It is an option that applies to the drm to allow linux binaries to
< said:
> This is needed for some programs. For example for Python 2.3cvs sets
> (among others) _POSIX_C_SOURCE 199506L, but also expects to have chroot
> and friends.
Then it's wrong. If it doesn't want a POSIX environment (evidently
not since it needs chroot()) then it shouldn't ask for one.
Are there any potential draw backs to enabling DRM_LINUX? Or should
DRM_LINUX be enabled whenever one enables COMPAT_LINUX?
This has not been clear to me from reading NOTES.
Thanks,
--Lucky Green
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of th
Marc Recht <[EMAIL PROTECTED]> writes:
> > I've had the attached patch in my tree for a while. I'll try and get
> > it and the patch committed today.
> Thanks! This solves some problems, but there are some left. Mostly socket
> and rpc related. For example PF_INET and friends are undefined..
Th
Unfortunately I can't provide much useful information, just the two
panic messages. At least in the trap case, the dmesg buffer will
include the trap stuff, but in plain panic cases, I don't have any
way to copy the trace stuff rom the box I saw these on, sigh.
Anyway...
In both cases, the files
Ray Kohler ([EMAIL PROTECTED]) wrote:
>
> I've sent mail to phoenix@ , but I thought I'd let this list
> know as well. Native phoenix works fine on -current for me,
> in spite of the Makefile claims. Install the perl5 port on a
> recent -current and phoenix will build and run perfectly. (And
> if
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> Please use a more descriptive subject line, fetch(1) is not in any way
> the cause of your problem.
Yes, the subject could have been more informative... Hope this one is
better.
As for the problem - it still crashes very reliably. I could try to
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
On Mon, 11 Nov 2002, David Schultz wrote:
> Thus spake Andre Albsmeier <[EMAIL PROTECTED]>:
> > It seems to be a Quantum Atlas drive. IIRC, I have several of them
> > running fine (I am not 100% sure, I am on holidays at the moment :-)).
> > You might want to check the firmware of that drive. I hav
Thus spake Andre Albsmeier <[EMAIL PROTECTED]>:
> It seems to be a Quantum Atlas drive. IIRC, I have several of them
> running fine (I am not 100% sure, I am on holidays at the moment :-)).
> You might want to check the firmware of that drive. I have upgraded
> the FW on my Quantum Atlas I and II d
On Mon, Nov 11, 2002 at 04:52:22PM +0100, Harti Brandt wrote:
AG>But does using a union make it safe?
> Well, I just had a long discussion with a collegue about the topic. The
> main problem is in the ISO-C standard, section 6.7 point 4 which states:
>
> All declarations in the same scope that re
TOMITA Yoshinori wrote:
> Yes, I agree with your example code.
>
> But unfortunately, that ugly code was contained in our inhouse library
> written by someone.
> It took me two days to debug and find out where difference comes from
> between gcc-2.95.4 and gcc-3.2.1.
And half a day to fire the pe
On 11-Nov-2002 Kris Kennaway wrote:
> I just got this on a Nov 1 current kernel:
>
> panic: sleeping thread owns a mutex
> Debugger("panic")
> Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
> db> bt
> No such command
> db> trace
> Debugger(c04038ad,c047e2c0,c0402a36,d928bb80,1) at Deb
Harti Brandt <[EMAIL PROTECTED]> writes:
> I just doscovered, that the -Wformat feature does not work for warn() and
> err(), but works for printf() und Co. Was the __printf0like feature not
> patched into the actual gcc?
Your system is out of date, I got a format error for a warn(3) call
earlier
Please use a more descriptive subject line, fetch(1) is not in any way
the cause of your problem.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
> [2] I simply cannot see us kldload'ing stuff in response to
> ls -l /dev/watchthis
In fact, I think a lot of people would get very angry if we did this,
as it might turn ls(1) into panic(1).
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
T
I just got this on a Nov 1 current kernel:
panic: sleeping thread owns a mutex
Debugger("panic")
Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
db> bt
No such command
db> trace
Debugger(c04038ad,c047e2c0,c0402a36,d928bb80,1) at Debugger+0x54
panic(c0402a36,1,c04029a2,6b,0) at panic+0xa
Harti Brandt <[EMAIL PROTECTED]> wrote:
>
> Yes, of course, but one would assume it to work (I suppose there is a
> large amount of code that assumes it will work).
Not a safe assumption at all. For example, what if the alignment
requirements for `short' and `int' are different (as they frequ
On Mon, 11 Nov 2002, Thomas David Rivers wrote:
TDR>Harti Brandt <[EMAIL PROTECTED]> wrote:
TDR>>
TDR>>
TDR>> Hmm, I though the following would work:
TDR>>
TDR>> void
TDR>> foo(unsigned short *s)
TDR>> {
TDR>> unsigned short temp;
TDR>>
TDR>> temp = s[0];
TDR>> s[0] = s[1];
TDR>> s[1] = te
Harti Brandt <[EMAIL PROTECTED]> wrote:
>
>
> Hmm, I though the following would work:
>
> void
> foo(unsigned short *s)
> {
> unsigned short temp;
>
> temp = s[0];
> s[0] = s[1];
> s[1] = temp;
> }
>
> main()
> {
> int i = 0x12345678;
>
> foo(&i);
> p
Hi,
i just compiled FreeBSD-current for test purposes but it hangs
at boot. The bootloader tries to load the kernel, but nothing
appears on the screen and the computer hangs. I must use the
reset button, Ctrl-Alt-Delete doesn't work.
I've done the last CVS-Update 3 hours ago, so the sources are p
On 09-Nov-2002 Joel M. Baldwin wrote:
>
> Since going from a SMP to nonSMP kernel the Hard Locks don't
> seem to be happening. However I'm getting panics.
>
> I've gotten 4 'sleeping thread owns a mutex' panics and one each
> of 'Assertion i != 0 failed at ../../../kern/subr_witness.c:669'
> an
> I've had the attached patch in my tree for a while. I'll try and get
> it and the patch committed today.
Thanks! This solves some problems, but there are some left. Mostly socket
and rpc related. For example PF_INET and friends are undefined..
> The whole point of the standards constants is t
Harti Brandt <[EMAIL PROTECTED]> wrote:
>
> Well, I just had a long discussion with a collegue about the topic. The
> main problem is in the ISO-C standard, section 6.7 point 4 which states:
>
> All declarations in the same scope that refer to the same object or
> function shall specify compatibl
On Mon, 11 Nov 2002, Andrew Gallatin wrote:
AG>
AG>Harti Brandt writes:
AG> > On Mon, 11 Nov 2002, TOMITA Yoshinori wrote:
AG> >
AG> > This is probably not a bug, but a feature. You are not expected to access
AG> > a variable through a pointer to a non-compatible type. int and short are
AG> > not
On Mon, 11-Nov-2002 at 01:49:18 -0800, David Schultz wrote:
> Thus spake David Schultz <[EMAIL PROTECTED]>:
> > I'm running into the same problems on a very light I/O load
> > (running /usr/bin/less on certain files triggers it). There's
> > also a timeout every time at bootup. I have included my
Thanks!
> It looks like has some XSI bugs. Is _XOPEN_SOURCE defined
> anywhere? If so, try the attached patch. If not, this is a bug in
Yes, _XOPEN_SOURCE is defined. So, it solves some of the problems.
> Python (since POSIX doesn't specify chroot()) and should be fixed at
> their end and in
Marc Recht <[EMAIL PROTECTED]> writes:
> Hi!
>
> I've made a small patch to make it possible to enable BSD extensions
> although _POSIX_SOURCE, _POSIX_C_SOURCE or _XOPEN_SOURCE has been
> defined. This is made with a new define _BSD_SOURCE right after the
> XOPEN_SOURCE handling. It sets __XSI_VI
David W. Chapman Jr. wrote:
> searching archive yields this thread.
'Subject: /usr/src/sys/netinet/udp_usrreq.c:290'
looks like I'm not the only one seeing this.
This happens on my test machine directly after samba starts ...
Can you disable samba from starting just to make sure it isn't
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Harti Brandt writes:
> On Mon, 11 Nov 2002, TOMITA Yoshinori wrote:
>
> This is probably not a bug, but a feature. You are not expected to access
> a variable through a pointer to a non-compatible type. int and short are
> not compatible. (see your ISO C standard on this topic).
>
> Try t
> searching archive yields this thread.
> >
> > 'Subject: /usr/src/sys/netinet/udp_usrreq.c:290'
> >
> > looks like I'm not the only one seeing this.
>
> This happens on my test machine directly after samba starts ...
Can you disable samba from starting just to make sure it isn't the cause?
T
>> On Mon, 11 Nov 2002 08:55:02 -0500 (EST), Thomas David Rivers <[EMAIL PROTECTED]>
>said:
Th> Several people have pointed out that using "volatile" will
Th> help with your code.
Th> But - even with the use of "volatile" - your code is invalid ANSI
Th> C.
--snip--
Thanks for your detailed
>
> For the source code below, compiling gcc -O2/-O3 seem to produce
> incorrect code.
>
> ---
> #include
> int main(int argc, char* argv[])
> {
> unsigned int x = 0x12345678;
> unsigned short tmp;
> printf("%x\n", x);
> tmp = ((unsigned short *)&x
>> On Mon, 11 Nov 2002 13:55:17 +0100, Poul-Henning Kamp
>> <[EMAIL PROTECTED]> said:
P> Your code forgot to tell the compiler that you would be messing
P> with the variables storage directly.
Thanks!
I have never dreamed to use "volatile" here.
As gcc-2.95.x -O2/-O3 was OK without volatile, I th
On Mon, 11 Nov 2002, TOMITA Yoshinori wrote:
This is probably not a bug, but a feature. You are not expected to access
a variable through a pointer to a non-compatible type. int and short are
not compatible. (see your ISO C standard on this topic).
Try to use ntohl(), htonl() for your problem.
h
In message <[EMAIL PROTECTED]>, TOMITA Yoshinori
writes:
>For the source code below, compiling gcc -O2/-O3 seem to produce
>incorrect code.
>
>---
>#include
>int main(int argc, char* argv[])
>{
>unsigned int x = 0x12345678;
>unsigned short tmp;
>printf(
For the source code below, compiling gcc -O2/-O3 seem to produce
incorrect code.
---
#include
int main(int argc, char* argv[])
{
unsigned int x = 0x12345678;
unsigned short tmp;
printf("%x\n", x);
tmp = ((unsigned short *)&x)[0];
((unsigned shor
Hi!
I've made a small patch to make it possible to enable BSD extensions
although _POSIX_SOURCE, _POSIX_C_SOURCE or _XOPEN_SOURCE has been
defined. This is made with a new define _BSD_SOURCE right after the
XOPEN_SOURCE handling. It sets __XSI_VISIBLE 600 and __BSD_VISIBLE 1.
This is needed for s
Hi!
I have two systems with a DLINK Gigabit Ethernet Card.
It doesn't work under CURRENT:
FreeBSD geclab2.mpe-garching.mpg.de 5.0-CURRENT FreeBSD 5.0-CURRENT #1:
Mon Nov 11 10:27:48 CET 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GECLAB2 i386
lge0: port 0xb000-0xb0ff \
mem 0xd000-0xd0
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Frustrated With Your Internet Marketing Efforts?
Have you tried:
FREE Classifieds? (Don't work)
Web Site? (Good for closing but you have to have visitors)
Banners? (Expensive and Iffy)
E-Zine? (They're great, but only with thousands of members)
Search Engines (Easy to be buried with thousand
Thus spake David Schultz <[EMAIL PROTECTED]>:
> I'm running into the same problems on a very light I/O load
> (running /usr/bin/less on certain files triggers it). There's
> also a timeout every time at bootup. I have included my dmesg
> below.
[...]
Here's some additional information:
# camcon
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
47 matches
Mail list logo
