On Mon, Jan 14, 2013 at 04:39:17PM -0500, John Baldwin wrote:
> This patch adds a new -r flag to dump the resource usage information (what
> you
> would get from getrusage() or wait()) for a given process. Sample output:
>
> % procstat -r $$
> PID COMM TYPE
On Tue, Jan 15, 2013 at 01:49:01PM +, David Chisnall wrote:
> On 15 Jan 2013, at 13:47, Slawa Olhovchenkov wrote:
>
> > maximum RSS -- 3328 _bytes_? You kidding.
>
> I think this is a bug in our getrusage. I've seen similar (<4KB)
> things in a program that mmap()s 12KB of input, allocates
On Monday, January 14, 2013 5:44:42 pm Konstantin Belousov wrote:
> On Mon, Jan 14, 2013 at 04:39:17PM -0500, John Baldwin wrote:
> > This patch adds a new -r flag to dump the resource usage information (what
you
> > would get from getrusage() or wait()) for a given process. Sample output:
> >
On Mon, Jan 14, 2013 at 06:48:13PM -0800, Garrett Cooper wrote:
> I tried using ktrace on a kernel compiled a week ago, and it appears
> to not be following forks like it should on amd64:
> # ktrace -d ./regress -l
> [snip]
> Not sure how it broke, but it was working a couple months ago (in
> par
hiren panchasara wrote this message on Tue, Jan 15, 2013 at 07:52 -0800:
> http://www.strugglingcoder.info/patches/clang_warnings_dev_bktr.txt
This patch does not look correct at all... It is simply removing code..
How is is good that after we failed to set the tv_freq that we continue
on?
What
John-Mark Gurney wrote this message on Tue, Jan 15, 2013 at 15:10 -0800:
> hiren panchasara wrote this message on Tue, Jan 15, 2013 at 07:52 -0800:
> > http://www.strugglingcoder.info/patches/clang_warnings_dev_bktr.txt
>
> This patch does not look correct at all... It is simply removing code..
>
It seems that buildworld depends on the existence of
/usr/bin/compile_et if one wants to build WITH_KERBEROS
on a system that has never had Kerberos support. I
discovered this issue when des@ removed the NOFOO and
NO_FOO options, and the NO_KERBEROS="YES" in my
/etc/make.conf was neutered. The sy
On Tue, Jan 15, 2013 at 3:22 PM, John-Mark Gurney wrote:
> John-Mark Gurney wrote this message on Tue, Jan 15, 2013 at 15:10 -0800:
>> hiren panchasara wrote this message on Tue, Jan 15, 2013 at 07:52 -0800:
>> > http://www.strugglingcoder.info/patches/clang_warnings_dev_bktr.txt
>>
>> This patch
On Tue, Jan 15, 2013 at 03:35:25PM -0800, Steve Kargl wrote:
> It seems that buildworld depends on the existence of
> /usr/bin/compile_et if one wants to build WITH_KERBEROS
> on a system that has never had Kerberos support. I
> discovered this issue when des@ removed the NOFOO and
> NO_FOO option
On Tue, Jan 15, 2013 at 06:44:39PM -0500, Glen Barber wrote:
> On Tue, Jan 15, 2013 at 03:35:25PM -0800, Steve Kargl wrote:
> > It seems that buildworld depends on the existence of
> > /usr/bin/compile_et if one wants to build WITH_KERBEROS
> > on a system that has never had Kerberos support. I
>
On Tue, Jan 15, 2013 at 04:46:01PM -0800, Steve Kargl wrote:
> > It actually gets quite worse from there.
>
> Yep. :(
> I just hit
>
> cc -O2 -pipe -march=opteron -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS
> -DOLD_ENVIRON -DENV_HACK -DSTREAMSPTY -DINET6
> -I/usr/src/libexec/telnetd/../../contrib/te
I am working on a fix for this. It shouldn't be too bad, as we already
build a cross-ctfconvert in certain cases. I just need to get some
machines running older FreeBSD versions to test on to confirm that the fix
worked. Should be able to test tomorrow, assuming that I am finally able
to coerce
I've just gotten this panic on a -CURRENT (r245473):
freebsd10-zfs dumped core - see /var/crash/vmcore.0
Tue Jan 15 20:32:15 CST 2013
FreeBSD freebsd10-zfs 10.0-CURRENT FreeBSD 10.0-CURRENT #2 r245473: Tue Jan 15
19:45:27 CST 2013 root@freebsd10-zfs:/usr/obj/usr/src/sys/BORG-DTRACE amd64
On Tue, Jan 15, 2013 at 2:53 PM, Jilles Tjoelker wrote:
> On Mon, Jan 14, 2013 at 06:48:13PM -0800, Garrett Cooper wrote:
>> I tried using ktrace on a kernel compiled a week ago, and it appears
>> to not be following forks like it should on amd64:
>
>> # ktrace -d ./regress -l
>> [snip]
>
>> Not s
Hi,
There doesn't seem to be a blessed way to set the baudrate from inside
gdb/kgdb. It seems to be set from '-b' on the command line.
However kgdb doesn't have this support.
This patch adds -b support so kgdb so I can override the default speed
(9600 it seems) to speak kgdb over serial to a 115
Also, I found 'set remotebaud' and 'set debug remote 1' to do this.
I'd like to add the code just to support the same -b flag as gdb (so
-r can also be used with a non-standard serial port.)
Thanks,
Adrian
On 15 January 2013 21:15, Adrian Chadd wrote:
> Hi,
>
> There doesn't seem to be a ble
16 matches
Mail list logo