Roland McGrath, le Thu 05 May 2011 11:05:20 -0700, a écrit :
> > That will tell me how the ports are connected between processes, but not
> > why.
>
> Indeed. But which ports they are usually leads you to the why.
Not necessarily. Without backtraces, I would probably never have
thought about fi
Samuel Thibault, le Thu 05 May 2011 18:45:12 +0200, a écrit :
> / ext2fs: ~9000, mostly receive
> pflocal: ~3, mostly send
> defaultpager: ~38000, mostly send
> chroot ext2fs: ~10, mostly receive
> pfinet: ~57000, mostly send
>
> I'll check what are the allocators of the send rights here.
> Roland McGrath, le Thu 05 May 2011 10:06:46 -0700, a écrit :
> > > What I can however observe is ports in other translators: after 17h
> > > building stuff, here are the number of ports:
> > >
> > > / ext2fs: ~9000, mostly receive
> > > pflocal: ~3, mostly send
> > > defaultpager: ~38000, m
Roland McGrath, le Thu 05 May 2011 10:06:46 -0700, a écrit :
> > What I can however observe is ports in other translators: after 17h
> > building stuff, here are the number of ports:
> >
> > / ext2fs: ~9000, mostly receive
> > pflocal: ~3, mostly send
> > defaultpager: ~38000, mostly send
> >
> What I can however observe is ports in other translators: after 17h
> building stuff, here are the number of ports:
>
> / ext2fs: ~9000, mostly receive
> pflocal: ~3, mostly send
> defaultpager: ~38000, mostly send
> chroot ext2fs: ~10, mostly receive
> pfinet: ~57000, mostly send
>
>
> However, when compiling the C code, a lot of warnings are issued about
> emacs using depreciated sigblock and sigsetmask functions. The
> recommended function to use now is sigprocmask.
That is true. However, there is only an actual difference if there are
more than 32 signal numbers available
On Thu, 2011-05-05 at 18:15 +0200, Samuel Thibault wrote:
> Svante Signell, le Thu 05 May 2011 17:02:27 +0200, a écrit :
> > The latest emacs version does not compile on GNU/Hurd. When trying with
> > default settings there is a segfault when compiling
> > lisp/cedet/srecode/mode.el using the built
Samuel Thibault, le Thu 05 May 2011 18:45:12 +0200, a écrit :
> Samuel Thibault, le Thu 05 May 2011 15:44:03 +0200, a écrit :
> > It could simply be symlinks, couldn't it? I don't see what translator
> > could be started. All that is possibly a bit non-standard is that we use
> > chroot a lot in a
Samuel Thibault, le Thu 05 May 2011 15:44:03 +0200, a écrit :
> It could simply be symlinks, couldn't it? I don't see what translator
> could be started. All that is possibly a bit non-standard is that we use
> chroot a lot in a secondary ext2fs (which is the one that is leaking,
> the / one is not
Svante Signell, le Thu 05 May 2011 17:02:27 +0200, a écrit :
> The latest emacs version does not compile on GNU/Hurd. When trying with
> default settings there is a segfault when compiling
> lisp/cedet/srecode/mode.el using the built emacs and dumped code.
> Changing the optimization of the C code
Hi,
The latest emacs version does not compile on GNU/Hurd. When trying with
default settings there is a segfault when compiling
lisp/cedet/srecode/mode.el using the built emacs and dumped code.
Changing the optimization of the C code from -O2 to -O0 resulted an
illegal instruction at the same file
Richard Braun, le Thu 05 May 2011 15:31:14 +0200, a écrit :
> On Thu, May 05, 2011 at 01:54:30PM +0200, Samuel Thibault wrote:
> > It's the big leak I have on the buildds. 50k ports after like 10h
> > building stuff.
>
> Assuming this leak only happens when starting a new translator, this
> implie
On Thu, May 05, 2011 at 01:54:30PM +0200, Samuel Thibault wrote:
> It's the big leak I have on the buildds. 50k ports after like 10h
> building stuff.
Assuming this leak only happens when starting a new translator, this
implies building stuff starts a lot of them. Identifying which ones
may help n
Svante Signell, le Thu 05 May 2011 14:37:11 +0200, a écrit :
> > No, that message is actually the converse of what I'm chasing.
>
> How to find out if ports are leaked? Which command to use?
portinfo
Samuel
On Thu, 2011-05-05 at 14:25 +0200, Samuel Thibault wrote:
> Svante Signell, le Thu 05 May 2011 14:02:52 +0200, a écrit :
> > On Thu, 2011-05-05 at 13:54 +0200, Samuel Thibault wrote:
> > > Richard Braun, le Thu 05 May 2011 12:32:00 +0200, a écrit :
> > > > Does this leak appear often ?
> > >
> > >
Svante Signell, le Thu 05 May 2011 14:02:52 +0200, a écrit :
> On Thu, 2011-05-05 at 13:54 +0200, Samuel Thibault wrote:
> > Richard Braun, le Thu 05 May 2011 12:32:00 +0200, a écrit :
> > > Does this leak appear often ?
> >
> > It's the big leak I have on the buildds. 50k ports after like 10h
> >
On Thu, 2011-05-05 at 13:54 +0200, Samuel Thibault wrote:
> Richard Braun, le Thu 05 May 2011 12:32:00 +0200, a écrit :
> > Does this leak appear often ?
>
> It's the big leak I have on the buildds. 50k ports after like 10h
> building stuff.
>
> > It seems to be triggered by starting a new transl
Richard Braun, le Thu 05 May 2011 12:32:00 +0200, a écrit :
> Does this leak appear often ?
It's the big leak I have on the buildds. 50k ports after like 10h
building stuff.
> It seems to be triggered by starting a new translator only.
So you are actually observing it too?
> I only took a quick
On Thu, May 05, 2011 at 12:55:46AM +0200, Samuel Thibault wrote:
> I've noticed a port leak on buildds when starting a translator. The
> backtrace of the port allocation is this:
>
> _ports_create_port_internal
> ports_create_port_noinstall
> diskfs_start_protid
> diskfs_create_protid
> diskfs_S_d
19 matches
Mail list logo
