Re: [PATCH] Add SF_ARCHIVED to EPERM in chflags(2) ERROR section

2010-10-29 Thread Jaakko Heinonen
On 2010-10-23, Garrett Cooper wrote: > The SF_ARCHIVED flag isn't noted in the chflags(2) ERROR section. > The attached patch adds the entry. > If no one has any objections, could someone help me commit this? > Index: lib/libc/sys/chflags.2 > ===

Re: [PATCH] Fix 'implicit declaration' warning and update vgone(9)

2010-10-29 Thread Robert Watson
On Wed, 27 Oct 2010, Benjamin Kaduk wrote: On Wed, 27 Oct 2010, Kostik Belousov wrote: On Wed, Oct 27, 2010 at 10:59:56AM -0400, Benjamin Kaduk wrote: [1] The old (racy) function is osi_TryEvictVCache, here: http://git.openafs.org/?p=openafs.git;a=blob;f=src/afs/FBSD/osi_vcache.c;h=c2060c74f0

Generating userland debugging symbols

2010-10-29 Thread Mark Johnston
Hello all, I've been working on some changes to the system build scripts that make it easier to create and install debugging symbols files for the base userland. What we do in the tree at my work (Sandvine) is use a script that invokes strip(1) and objcopy(1) to create a separate file containing t

Re: Generating userland debugging symbols

2010-10-29 Thread Kostik Belousov
On Fri, Oct 29, 2010 at 03:18:27PM -0400, Mark Johnston wrote: > Hello all, > > I've been working on some changes to the system build scripts that make > it easier to create and install debugging symbols files for the base > userland. What we do in the tree at my work (Sandvine) is use a script >

[PATCH] hwpmc(4) syscall arguments fix

2010-10-29 Thread Oleksandr Tymoshenko
I ran into problems trying to get hwpmc to work on 64-bit MIPS system with big endian byte order. Turned out hwpmc syscall handler is byte-order and register_t size agnostic unlike the rest of syscalls. The best solution I have so far is a copy sys/sysproto.h approach: http://people.freebsd.or

Re: Generating userland debugging symbols

2010-10-29 Thread Garrett Cooper
On Fri, Oct 29, 2010 at 4:39 PM, Kostik Belousov wrote: > On Fri, Oct 29, 2010 at 03:18:27PM -0400, Mark Johnston wrote: >> Hello all, >> >> I've been working on some changes to the system build scripts that make >> it easier to create and install debugging symbols files for the base >> userland.

Re: Generating userland debugging symbols

2010-10-29 Thread Mark Johnston
On Sat, Oct 30, 2010 at 02:39:00AM +0300, Kostik Belousov wrote: > I do think that something like this would be useful. But, shouldn't > the DEBUG_FLAGS be also involved in the patch ? The goal would be > to have debug symbols for userland staff. esp. the libraries, > handled in a similar manner to

Re: Generating userland debugging symbols

2010-10-29 Thread Mark Johnston
On Fri, Oct 29, 2010 at 06:05:08PM -0700, Garrett Cooper wrote: > But having a strip script might be useful. Some companies brand > binaries for their own purposes, so having a hook into a strip script > (it should be no more than a few lines), should suffice. Something > that my old group used

Re: Generating userland debugging symbols

2010-10-29 Thread Garrett Cooper
On Fri, Oct 29, 2010 at 7:10 PM, Mark Johnston wrote: > On Fri, Oct 29, 2010 at 06:05:08PM -0700, Garrett Cooper wrote: >>     But having a strip script might be useful. Some companies brand >> binaries for their own purposes, so having a hook into a strip script >> (it should be no more than a fe

Re: Generating userland debugging symbols

2010-10-29 Thread Mark Johnston
On Fri, Oct 29, 2010 at 07:48:31PM -0700, Garrett Cooper wrote: > On Fri, Oct 29, 2010 at 7:10 PM, Mark Johnston wrote: > > On Fri, Oct 29, 2010 at 06:05:08PM -0700, Garrett Cooper wrote: > > > > That's almost exactly what we're doing. I also think it's easier to go with > > a > > script, but the

Re: Generating userland debugging symbols

2010-10-29 Thread Garrett Cooper
On Fri, Oct 29, 2010 at 8:35 PM, Mark Johnston wrote: > On Fri, Oct 29, 2010 at 07:48:31PM -0700, Garrett Cooper wrote: >> On Fri, Oct 29, 2010 at 7:10 PM, Mark Johnston wrote: >> > On Fri, Oct 29, 2010 at 06:05:08PM -0700, Garrett Cooper wrote: >> > >> > That's almost exactly what we're doing. I