me = "/home", '\0' }, mnt_cred = 0xc5aaed00,
mnt_data = 0xc5a99e00, mnt_time = 0, mnt_iosize_max = 131072,
mnt_export = 0x0, mnt_mntlabel = 0x0, mnt_fslabel = 0x0,
mnt_nvnodelistsize = 10746, mnt_hashseed = 1412285663, mnt_markercnt = 0,
mnt_holdcnt = 0, mnt_holdcntwaiters = 0, mnt_se
utils/portconf might allow you to do what you want. I just use the
following construct in make.conf though, and it seems to work.
.if ${.CURDIR:M*/category/port}
or
.if ${.CURDIR:M*/category/port*}
put port specific defines here
.endif
BTW, questions like this probably are best served on que
Micah wrote:
Kostik Belousov wrote:
On Thu, Oct 26, 2006 at 09:22:43AM -0700, Micah wrote:
Kostik Belousov wrote:
I saw several similar reports.
Please, submit me the output of the "print *mp" in the same frame.
Also, I'm interested in kernel config.
Is the problem reproduc
Kostik Belousov wrote:
On Thu, Oct 26, 2006 at 09:22:43AM -0700, Micah wrote:
Kostik Belousov wrote:
I saw several similar reports.
Please, submit me the output of the "print *mp" in the same frame.
Also, I'm interested in kernel config.
Is the problem reproducible ?
It see
Kostik Belousov wrote:
I saw several similar reports.
Please, submit me the output of the "print *mp" in the same frame.
Also, I'm interested in kernel config.
Is the problem reproducible ?
It seems now that any time I compile openoffice the system will
eventually panic. Other disk intensi
valid address I was able
to get another crashdump, but kgdb locked up while trying to read it.
Thanks,
Micah
Micah wrote:
Can anyone help me in deciphering what this crashdump is telling me? My
i386 6.1p3 system is panicking under heavy IO load and I'm trying to
isolate the cause. I
Can anyone help me in deciphering what this crashdump is telling me? My
i386 6.1p3 system is panicking under heavy IO load and I'm trying to
isolate the cause. I've never debugged a crashdump before, so if there's
more information I can milk from the core file, let me know.
M. Warner Losh wrote:
In message: <[EMAIL PROTECTED]>
Micah <[EMAIL PROTECTED]> writes:
: #define MAXNAMLEN 255
: chard_name[MAXNAMLEN + 1]; /* name must be no longer than
: this */
: #if !__BSD_VISIBLE
: #undef MAXNAMLEN
: #endif
: };
: I'm not
AXNAMLEN
#endif
};
I'm not sure if it's more readable, but it puts 255 in only one location.
- Micah
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
9 matches
Mail list logo