Experiments with dummynet shown ineffective support for very short
tick-based callouts. New version fixes that, allowing to get as many
tick-based callout events as hz value permits, while still be able to
aggregate events and generating minimum of interrupts.
Also this version modifies
TB --- 2012-12-18 07:30:00 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-18 07:30:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
I checked out head Sunday and now my attempt at building a kernel says:
ERROR: ctfconvert: failed to initialize DWARF: Unimplemented code at
[dwarf_init_attr(400)]
on every module it compiles (though it seems happy enough to keep
compiling). Should I just ignore this?-- George
On 2012-12-18 12:30, George Mitchell wrote:
I checked out head Sunday and now my attempt at building a kernel says:
ERROR: ctfconvert: failed to initialize DWARF: Unimplemented code at
[dwarf_init_attr(400)]
on every module it compiles (though it seems happy enough to keep
compiling). Should
TB --- 2012-12-18 07:30:00 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-18 07:30:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
Hi,
the following backtrace is from a crash that happened when building
www/chromium with clang. The chromium port builds a binary protoc which
crashes when built with clang.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 802006400 (LWP 100869)]
0x000800996506 in
On Mon, Dec 17, 2012 at 01:22:59PM -0800, Adrian Chadd wrote:
Personally, I'd rather see some consistently used units here..
bintime (or something similar) is the correct choice here.
If we are concerned about the size (128 bit) then we
can map it to a shorter, fixed point format, such
as
On Tue, Dec 18, 2012 at 01:21:42PM +0100, Ren? Ladan wrote:
Hi,
the following backtrace is from a crash that happened when building
www/chromium with clang. The chromium port builds a binary protoc which
crashes when built with clang.
Program received signal SIGSEGV, Segmentation fault.
TB --- 2012-12-18 07:30:00 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-18 07:30:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
On Mon, Dec 17, 2012 at 11:03:53PM +0200, Alexander Motin wrote:
Hi.
I would instead do the following:
I also don't very like the wide API and want to hear fresh ideas, but
approaches to time measurement there are too different to do what you
are proposing. Main problem is that while
On Tue, Dec 18, 2012 at 06:36:43PM +0100, Luigi Rizzo wrote:
On Mon, Dec 17, 2012 at 11:03:53PM +0200, Alexander Motin wrote:
...
So I believe my proposal would give large simplifications in
the code and lead to a much cleaner implementation of what
you have designed:
1. acknowledge the
On 18.12.2012 19:36, Luigi Rizzo wrote:
On Mon, Dec 17, 2012 at 11:03:53PM +0200, Alexander Motin wrote:
I would instead do the following:
I also don't very like the wide API and want to hear fresh ideas, but
approaches to time measurement there are too different to do what you
are proposing.
==90885== Memcheck, a memory error detector
==90885== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==90885== Using Valgrind-3.8.0 and LibVEX; rerun with -h for copyright info
==90885== Command: ./protoc
==90885==
==90885== Invalid read of size 8
==90885==at 0x1388506:
On 2012-12-18 13:21, René Ladan wrote:
the following backtrace is from a crash that happened when building
www/chromium with clang. The chromium port builds a binary protoc which
crashes when built with clang.
...
So the question is if this is a protoc or a clang or a libstdc++ bug.
Try
Try removing --gc-sections from the link flags for protoc, that should
solve it for now. I am still looking at the root cause, which seems to
be something in our ld; it does not seem to be related to either clang
or libstdc++.
Whoa, thank you! Removing --gc-sections from the link flags
I have a checkout of r244047. I did a make kernel-toolchain followed by a
make buildkernel and I see this warning.
On Tue, Dec 18, 2012 at 7:15 AM, Dimitry Andric d...@freebsd.org wrote:
On 2012-12-18 12:30, George Mitchell wrote:
I checked out head Sunday and now my attempt at building a
On 18.12.2012 20:03, Alexander Motin wrote:
On 18.12.2012 19:36, Luigi Rizzo wrote:
On Mon, Dec 17, 2012 at 11:03:53PM +0200, Alexander Motin wrote:
I would instead do the following:
I also don't very like the wide API and want to hear fresh ideas, but
approaches to time measurement there
On 2012-12-18 22:37, Ryan Stone wrote:
On Tue, Dec 18, 2012 at 7:15 AM, Dimitry Andric d...@freebsd.org
mailto:d...@freebsd.org wrote:
On 2012-12-18 12:30, George Mitchell wrote:
ERROR: ctfconvert: failed to initialize DWARF: Unimplemented code at
[dwarf_init_attr(400)]
On Tue, Dec 18, 2012 at 4:56 PM, Dimitry Andric d...@freebsd.org wrote:
The question is if ctfconvert (and dependencies) are rebuilt when you do
kernel-toolchain. Can you figure out if it runs ctfconvert from base?
Aha! You're right:
[rstone@rstone-laptop vll]make buildenv
Entering world
[top posting for readability;
in summary we were discussing the new callout API trying to avoid
an explosion of methods and arguments while at the same time
supporting the old API and the new one]
(I am also Cc-ing phk as he might have better insight
on the topic).
I think the patch you propose
On Tue, 2012-12-18 at 23:58 +0100, Luigi Rizzo wrote:
[top posting for readability;
in summary we were discussing the new callout API trying to avoid
an explosion of methods and arguments while at the same time
supporting the old API and the new one]
(I am also Cc-ing phk as he might have
On Tue, Dec 18, 2012 at 04:27:45PM -0700, Ian Lepore wrote:
On Tue, 2012-12-18 at 23:58 +0100, Luigi Rizzo wrote:
[top posting for readability;
in summary we were discussing the new callout API trying to avoid
an explosion of methods and arguments while at the same time
supporting the old
On Wed, 2012-12-19 at 00:29 +0100, Luigi Rizzo wrote:
On Tue, Dec 18, 2012 at 04:27:45PM -0700, Ian Lepore wrote:
On Tue, 2012-12-18 at 23:58 +0100, Luigi Rizzo wrote:
[top posting for readability;
in summary we were discussing the new callout API trying to avoid
an explosion of
On Tue, Dec 18, 2012 at 04:37:10PM -0700, Ian Lepore wrote:
On Wed, 2012-12-19 at 00:29 +0100, Luigi Rizzo wrote:
On Tue, Dec 18, 2012 at 04:27:45PM -0700, Ian Lepore wrote:
On Tue, 2012-12-18 at 23:58 +0100, Luigi Rizzo wrote:
[top posting for readability;
in summary we were
On 12/18/12 07:15, Dimitry Andric wrote:
On 2012-12-18 12:30, George Mitchell wrote:
I checked out head Sunday and now my attempt at building a kernel says:
ERROR: ctfconvert: failed to initialize DWARF: Unimplemented code at
[dwarf_init_attr(400)]
on every module it compiles (though it seems
On Fri, Dec 7, 2012 at 12:42 PM, Kimmo Paasiala kpaas...@gmail.com wrote:
Hello,
I wrote a small patch for /etc/network.subr to add support for
ipv6_addrs_IF aliases in rc.conf(5) to match the already existing
ipv4_addrs_IF aliases for ipv4 addresses. With this patch the ipv6
aliases can be
26 matches
Mail list logo
