On 16 May 1999 at 12:47, Poul-Henning Kamp wrote:
> This is by intention:
>
> cd /sys/kern
> grep -i deadc0de *
> kern_malloc.c:#define WEIRD_ADDR0xdeadc0de
For those who like such factoids, AIX uses 0xdeadbeef similarly
for uninitialized data. Prior to FreeBSD 2.1.0,
In message <199905161034.maa00...@oranje.my.domain>, Marc van Woerkom writes:
>> fault virtual address = 0xdeadc0de
>
>0xdeadc0de - dead code? :-)
>
>Is this address a coincidence or a special crafted one?
This is by intention:
cd /sys/kern
grep -i deadc0de *
kern_mallo
> fault virtual address = 0xdeadc0de
0xdeadc0de - dead code? :-)
Is this address a coincidence or a special crafted one?
Regards,
Marc
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
> > One system was running 2.2.8, and my core file presents me with this:
...
> Just out of curiosity, are either of these systems running with NCR
> controllers?
In case you're fishing, I'm running 4 NCR equipped boxes (510 and 575)
with FreeBSD 2.2.8-stable right now and have seen *NO* problems
>
>
> I had two systems reboot at nearly the same time. (30 seconds apart), and
> are completely unrelated.
These both look like stack damage, actually.
> One system was running 2.2.8, and my core file presents me with this:
>
> su-2.02# gdb -k
> GDB is free software and you are welcome to dis
I had two systems reboot at nearly the same time. (30 seconds apart), and
are completely unrelated.
One system was running 2.2.8, and my core file presents me with this:
su-2.02# gdb -k
GDB is free software and you are welcome to distribute copies of it
under certain conditions; type "show cop
