> (while none I have ever seen actually do, the
> malloc implementation is free to retrn the memory to the kernel, and
> remove it from the process's address space).
FWIW, both old and new jemalloc are capable of doing this. :-)
.mrg.
Updating src tree:
P src/crypto/external/bsd/openssl/dist/crypto/armcap.c
P src/crypto/external/bsd/openssl/lib/libcrypto/arch/powerpc/ppccpuid.S
P src/crypto/external/bsd/openssl/lib/libcrypto/arch/powerpc64/ppccpuid.S
P src/lib/libcurses/get_wch.c
P src/lib/libcurses/getch.c
P
Date:Wed, 13 Mar 2019 11:44:51 -0700
From:Jason Thorpe
Message-ID: <9a2a4a34-35b0-490e-9a92-aab44174f...@me.com>
| Ok, well, I see some problematic code in sys_mlock() and sys_munlock(),
| but I don't think it's affecting this case (and it may in fact have
|
Date:Wed, 13 Mar 2019 10:37:41 -0700
From:Brian Buhrow
Message-ID: <201903131737.x2dhbfd8001...@lothlorien.nfbcal.org>
| Given this code fragment and the discussion you raise
| about it, allow me to ask what perhaps is a naive question. If the sample
| you
rhia...@falu.nl (Rhialto) writes:
>in the set is allocated and initialized. The set of blocks that may
>be allocated to inodes is held as part of the free-space reserve
>until all other space in the filesystem is allocated. Only then can
>it be used for file data.=20
>But the bit
I was reading about the history of the Unix File System. In
https://www.usenix.org/legacy/events/bsdcon03/tech/full_papers/mckusick/mckusick_html/
"Enhancements to the Fast Filesystem To Support Multi-Terabyte Storage
Systems"
there is this in section
4.1. Dynamic Inodes
One of the
On Wed, Mar 13, 2019 at 11:32:05AM +, Chavdar Ivanov wrote:
> Setting INSTALL_UNSTRIPPED=yes didn't work for me for zsh and ncurses,
> I still had to find all the '-s' flags in the install command
> invocations. Perhaps I am doing something wrong. Still, I've gor now
> zsh with the debug
> On Mar 13, 2019, at 10:27 AM, Robert Elz wrote:
>
> Some progress.
>
> #1 touching the buffer that malloc() returns (which is page aligned)
> made no difference - it is likely that the malloc llibrary would have
> done that in any case (the malloc is for just one page, so either it
> is
hello Robert. Given this code fragment and the discussion you raise
about it, allow me to ask what perhaps is a naive question. If the sample
you quote is incorrect, what is the correct way to accomplish the same
task?
-thanks
-Brian
On Mar 13, 6:27pm, Robert Elz wrote:
} Subject: Re:
Some progress.
#1 touching the buffer that malloc() returns (which is page aligned)
made no difference - it is likely that the malloc llibrary would have
done that in any case (the malloc is for just one page, so either it
is resident (or paged) or it is a ZFoD page, and most likely not the
Awesome, thanks! That's a thing which pops up from time to time, I've
had it myself.
On Wed, 13 Mar 2019 at 15:04, Patrick Welche wrote:
>
> On Tue, Mar 12, 2019 at 05:17:10PM +, Chavdar Ivanov wrote:
> > /etc/ttys ?
>
> Absolutely right. This laptop's xdm worked before the update, so I
On Tue, Mar 12, 2019 at 05:17:10PM +, Chavdar Ivanov wrote:
> /etc/ttys ?
Absolutely right. This laptop's xdm worked before the update, so I doubted
your suggestion.
What happened is that the update replaced my /etc/X11/xdm/Xservers.ws
in which I had carefully set vt08 as the terminal to
In article <20190313104136.gb58...@imac7.ub.uni-mainz.de>,
K. Schreiner wrote:
>Hi,
>
>I've had "build.sh ... distribution" failing on an amd64-VM running in
>VirtualBox (newest test version) like so:
>
>...
>: /u/NetBSD/src/external/bsd/jemalloc/lib/../dist/src/arena.c:647:
>Failed assertion:
s/gor/got/.
On the other hand there were some jemalloc changes overnight, so I
will update the system first and then try to get zsh crashes.
On Wed, 13 Mar 2019 at 11:32, Chavdar Ivanov wrote:
>
> Setting INSTALL_UNSTRIPPED=yes didn't work for me for zsh and ncurses,
> I still had to find all
Setting INSTALL_UNSTRIPPED=yes didn't work for me for zsh and ncurses,
I still had to find all the '-s' flags in the install command
invocations. Perhaps I am doing something wrong. Still, I've gor now
zsh with the debug options and all modules plus ncurses unstripped.
Now to build the OS debug
Date:Wed, 13 Mar 2019 10:06:42 +
From:Chavdar Ivanov
Message-ID:
| I saw the one with the trashed history as well.
|
| I don't think it is zsh's problem, though. As I mentioned above, I've
| used v5.7 since it came out without any problems until perhaps
On Wed, Mar 13, 2019 at 11:54:11AM +0100, Martin Husemann wrote:
> On Wed, Mar 13, 2019 at 10:44:46AM +, Patrick Welche wrote:
> > I stared at /etc/X11/xdm/Xresources, and
> > https://gitlab.freedesktop.org/xorg/app/xdm/blob/master/config/Xresources.in
> > and didn't spot additional fields
Päivitä tilisi
Tietojemme mukaan tiliäsi ei ole päivitetty, mikä on saattanut johtaa tilisi
sulkemiseen. Jos et päivitä tiliäsi, et voi enää lähettää ja vastaanottaa
sähköpostiviestejä, ja et saa pääsyä moniin uusimpiin keskusteluihin,
yhteystietoihin ja liitteisiin.
Päivitä tili nopeammin
On Wed, Mar 13, 2019 at 10:44:46AM +, Patrick Welche wrote:
> I stared at /etc/X11/xdm/Xresources, and
> https://gitlab.freedesktop.org/xorg/app/xdm/blob/master/config/Xresources.in
> and didn't spot additional fields (just our fonts are smaller and we
> fiddle with the NetBSD logo) - what
On Wed, Mar 13, 2019 at 08:10:23AM +1100, matthew green wrote:
> Patrick Welche writes:
> > Had a go with the shiny new X (thanks!) on the sandy bridge laptop
> > which no longer likes SNA but works with UX, and xdm seems to sit
> > at the prompt waiting for something:
> > ...
> is it a black
Hi,
I've had "build.sh ... distribution" failing on an amd64-VM running in
VirtualBox (newest test version) like so:
...
: /u/NetBSD/src/external/bsd/jemalloc/lib/../dist/src/arena.c:647:
Failed assertion: "nstime_compa\ re(>epoch, ) <= 0"
...
[1] Abort trap (core dumped)
Thanks. One has to read the manuals from time to time...
On Wed, 13 Mar 2019 at 10:21, Patrick Welche wrote:
>
> On Wed, Mar 13, 2019 at 10:06:42AM +, Chavdar Ivanov wrote:
> > I saw the one with the trashed history as well.
> >
> > I don't think it is zsh's problem, though. As I mentioned
On Wed, Mar 13, 2019 at 10:06:42AM +, Chavdar Ivanov wrote:
> I saw the one with the trashed history as well.
>
> I don't think it is zsh's problem, though. As I mentioned above, I've
> used v5.7 since it came out without any problems until perhaps 3-4
> days ago.
>
> I tried to build zsh
OK, I understand. I should carry on using it to see if it will break
again and perhaps get something useful.
On Wed, 13 Mar 2019 at 10:09, Martin Husemann wrote:
>
> On Wed, Mar 13, 2019 at 10:06:42AM +, Chavdar Ivanov wrote:
> > I saw the one with the trashed history as well.
> >
> > I
On Wed, Mar 13, 2019 at 10:06:42AM +, Chavdar Ivanov wrote:
> I saw the one with the trashed history as well.
>
> I don't think it is zsh's problem, though. As I mentioned above, I've
> used v5.7 since it came out without any problems until perhaps 3-4
> days ago.
It still is very likely a
I saw the one with the trashed history as well.
I don't think it is zsh's problem, though. As I mentioned above, I've
used v5.7 since it came out without any problems until perhaps 3-4
days ago.
I tried to build zsh with debug (adding --enable-zsh-debug
--enable-zsh-mem --enable-zsh-mem-debug
OK, with DIAGNOSTIC enabled, and with this patch made:
--- uvm_page.c 19 May 2018 15:03:26 - 1.198
+++ uvm_page.c 13 Mar 2019 08:51:11 -
@@ -1605,9 +1605,11 @@
uvm_pageunwire(struct vm_page *pg)
{
KASSERT(mutex_owned(_pageqlock));
+ KASSERT(pg->wire_count != 0);
On Wed, Mar 13, 2019 at 03:22:27PM +0700, Robert Elz wrote:
> [...]
>
> netbsd# df /tmp
> Filesystem1K-blocks Used Avail %Cap Mounted on
> tmpfs 4 4 0 100% /tmp
>
> That's what it showed (it was still in my xterm scrollback buffer from
> the
Date:Tue, 12 Mar 2019 23:21:59 -0700
From:Jason Thorpe
Message-ID:
| THAT is particularly special, because the code in question is:
|
|
| void
| uvm_pagewire(struct vm_page *pg)
| {
| KASSERT(mutex_owned(_pageqlock));
| #if
Date:Tue, 12 Mar 2019 23:21:59 -0700
From:Jason Thorpe
Message-ID:
Thanks for the reply. I have dropped tech-kern and tech-userlevel
from this reply though.
| The test employs a bogus understanding of how malloc() is specified.
Yes, that is kind of obvious,
> On Mar 12, 2019, at 9:09 PM, Robert Elz wrote:
>
> The first issue I noticed, is that t_mlock() apparently belives
> the malloc(3) man page, which states:
>
> The malloc() function allocates size bytes of uninitialized memory. The
> allocated space is suitably aligned (after
31 matches
Mail list logo
