Bug #2088

bash stalling

Added by matthiasr almost 3 years ago. Updated almost 3 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

when re-building packages, the build process sometimes just … stops. There is no error or
anything, there's just nothing happening any more.

Examples of this are devel/scmgit-docs and x11/gtk2. The exact spot when this happens varies,
but I noticed that it's always (as far as I can tell) a bash process that stalls.

scmgit-docs repeatedly calls xmlto, which is a bash script. gtk2 uses bash for the configure
scripts (which more often than not stall at writing config.status or similar).

I have tried recompiling bash and installing the binary bash via pkg_radd; none helped.

I'm using a very recent (post-vm_object work) kernel, uname -a is:
DragonFly zz.2pktfkt.net 2.11-DEVELOPMENT DragonFly v2.11.0.358.ga17ae-DEVELOPMENT #4: Sun Jun
12 17:15:25 CEST 2011 :/usr/obj/usr/src/sys/X86_64_GENERIC x86_64

On my i386 UP laptop it seems to work fine (scmgit-docs build went through on first try).

History

#1 Updated by matthiasr almost 3 years ago

I just had the same problem during the install phase of net/avahi, so it's not
just bash.

#2 Updated by sepherosa almost 3 years ago

On Tue, Jun 14, 2011 at 6:41 PM, Matthias Rampke (via DragonFly issue
tracker) <> wrote:
>
> Matthias Rampke <> added the comment:
>
> I just had the same problem during the install phase of net/avahi, so it's not
> just bash.

I suggest you to move the source tree to at least:
0bc41be71b9d611ff86552e8ada125e0e9ac68bf

Best Regards,
sephe

#3 Updated by matthiasr almost 3 years ago

Still the same on v2.11.0.392.g192e9-DEVELOPMENT. Any ideas on how to find out
what is happening?

#4 Updated by matthiasr almost 3 years ago

... and it's fixed in v2.11.0.395.g15891-DEVELOPMENT.

#5 Updated by dillon almost 3 years ago

:Matthias Rampke <> added the comment:
:
:... and it's fixed in v2.11.0.395.g15891-DEVELOPMENT.
:
:----------
:status: chatting -> resolved

There are probably more of these sorts of issues with the recent VM work,
and I expect more to crop up as we shift from the use of the global vmobj
and vm tokens to fine-grained tokens. But they are getting resolved
in fairly short order.

-Matt
Matthew Dillon
<>

Also available in: Atom PDF