git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeffrey Walton <noloader@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Git port to Debian SH4 may have trouble
Date: Tue, 29 Nov 2022 17:33:34 -0500	[thread overview]
Message-ID: <CAH8yC8kpkcr3mk_XU-vz8QPX45O6K+bbfB8t_mRU37_R7=gDFQ@mail.gmail.com> (raw)
In-Reply-To: <Y4aEPpQsS8QxBYly@coredump.intra.peff.net>

On Tue, Nov 29, 2022 at 5:14 PM Jeff King <peff@peff.net> wrote:
>
> On Tue, Nov 29, 2022 at 04:49:30PM -0500, Jeffrey Walton wrote:
>
> > > Just a hunch, but does:
> > >
> > >   git config --global pack.threads 1
> > >
> > > help? The delta resolution is multi-threaded, but nothing else in the
> > > clone should be.
> >
> > Yes, `git config --global pack.threads 1` allowed things to continue.
> > The check-out was successful.
>
> OK, that narrows it down. The question then is why threads don't work.
> Is there something broken with threading or luck primitives on that
> platform? Or are we doing something sketchy with concurrency that
> happens to work on Intel but not elsewhere, and we end up in some kind
> of deadlock?

Probably something broken with the port. Or that's what I would put my money on.

> I suspect if we want to know more, you'd need to use gdb to grab a
> backtrace for each of the threads during the hang to see what they're
> trying to do.

Yeah, so GDB won't install at the moment. I tried earlier today. It
has some unsatisfied dependencies. Failure to build from source
(FTBFS), iirc.

Jeff

      reply	other threads:[~2022-11-29 22:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 17:01 Git port to Debian SH4 may have trouble Jeffrey Walton
2022-11-29 19:02 ` Jeff King
2022-11-29 21:49   ` Jeffrey Walton
2022-11-29 22:14     ` Jeff King
2022-11-29 22:33       ` Jeffrey Walton [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH8yC8kpkcr3mk_XU-vz8QPX45O6K+bbfB8t_mRU37_R7=gDFQ@mail.gmail.com' \
    --to=noloader@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).