I naively tried to build something with -fsanitize=address using llvm-4.0
port available on OpenBSD 6.1-amd64. I was immediately greeted with:
clang-4.0: error: unsupported option '-fsanitize=address' for target
'amd64-unknown-openbsd6.1'
How deep a rat hole does one have to go to port ASan to
> Date: Sun, 30 Apr 2017 21:53:40 +0200
> From: Martin Pieuchot
>
> We don't run on ARM < v7 anymore, so this can die.
>
> ok?
ok kettenis@
> Index: uvm/uvm_glue.c
> ===
> RCS file: /cvs/src/sys/uvm/uvm_glue.c,v
> retrieving revis
Index: amd64/conf/GENERIC
===
RCS file: /cvs/src/sys/arch/amd64/conf/GENERIC,v
retrieving revision 1.442
diff -u -p -u -p -r1.442 GENERIC
--- amd64/conf/GENERIC 12 Mar 2017 21:31:18 - 1.442
+++ amd64/conf/GENERIC 30 Apr 20
We don't run on ARM < v7 anymore, so this can die.
ok?
Index: uvm/uvm_glue.c
===
RCS file: /cvs/src/sys/uvm/uvm_glue.c,v
retrieving revision 1.72
diff -u -p -r1.72 uvm_glue.c
--- uvm/uvm_glue.c 30 Apr 2017 13:04:49 - 1.
Back in the old CSRG times, in the 80s, before the introduction of
PCATCH and tsleep(9), PZERO was a clever hack. The following comment
from sleep() in kern/kern_synch.c 3.1 explains it well:
* The most important effect of pri is that when
* pri<=PZERO a signal cannot disturb the
> Date: Sun, 30 Apr 2017 16:54:15 +0200
> From: Martin Pieuchot
>
> I'd like to rename DDB's entry point to be able to filter it out from
> the list of symbols to instrument. All Elf symbols prefixed with 'db_'
> will be invisible from the dynamic tracing tool I'm working on.
>
> This consolida
Sure. The Mach name has always bothered me.
I'd like to rename DDB's entry point to be able to filter it out from
the list of symbols to instrument. All Elf symbols prefixed with 'db_'
will be invisible from the dynamic tracing tool I'm working on.
This consolidate the approach taken by ddb(4) where having a db_printf()
allows you to instr
On Sun, Apr 30, 2017 at 03:04:38PM +0200, Mark Kettenis wrote:
> Here is a diff that makes mainbus(4) behave in a similar way as
> simplebus(4). Needed for the Firefly-RK3399 since it attaches most
> devices directly on mainbus(4) and need to control the order a bit.
>
> I dropped the "no device
Here is a diff that makes mainbus(4) behave in a similar way as
simplebus(4). Needed for the Firefly-RK3399 since it attaches most
devices directly on mainbus(4) and need to control the order a bit.
I dropped the "no device tree" panic. We really can't get this far
without having an FDT.
I'll d
This is a work-in-progres, now is the time to shoot holes thru it.
Basically, clang in base comes with libc++, which tends to not be
compatible with stuff compiled with gcc4 or clang from ports.
So I tried designing an interface to choose the most appropriate compiler
for most cases. The only tri
Hi,
A friend, who is fairly new to OpenBSD, was having some problems
upgrading the packages on his system.
The problem was that the upgrade guide doesn't make it totally clear
that `pkg_add -u` should be run after applying the configuration
changes. This matters for 6.1 as you need to migrate fro
12 matches
Mail list logo