From: Jeff King <peff@peff.net>
To: Bryan Turner <bturner@atlassian.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: Puzzling Git backtrace
Date: Wed, 27 Mar 2019 21:49:58 -0400 [thread overview]
Message-ID: <20190328014957.GA7887@sigill.intra.peff.net> (raw)
In-Reply-To: <CAGyf7-F8cmzOuhi6zeJJ13iwGh_ie-uTiJYUzBwssvH+kCY+yA@mail.gmail.com>
On Wed, Mar 27, 2019 at 05:49:27PM -0700, Bryan Turner wrote:
> I'm trying to assist a Bitbucket Server customer who is seeing some
> "git-upload-pack" processes "hang" on their server.
>
> While investigating, we had them connect gdb to their processes (which
> are 2.10.0 built from source using a simple unzip-and-run-make
> approach) and get the backtraces for them. The output that they're
> seeing makes no sense to me, though, so I'm throwing this out to the
> list just to see if anyone has any idea how the processes could end up
> like this.
upload-pack didn't become a builtin until v2.18, so...
> When they attached to 32433 and printed its backtrace, though, things
> go a little sideways:
>
> (gdb) attach 32433
> Attaching to program: /usr/bin/git, process 32433
The debugger needs to be using git-upload-pack as its executable, not
"git".
> (gdb) bt
> #0 0x00007f79d1aca240 in ?? ()
> #1 0x000000000045179e in mktree_line (allow_missing=4,
> nul_term_line=0, len=<optimized out>, buf=<optimized out>) at
> builtin/mktree.c:103
> #2 cmd_mktree (ac=<optimized out>, av=<optimized out>,
> prefix=<optimized out>) at builtin/mktree.c:173
> #3 0x0000000000000000 in ?? ()
And all of this is just trash, because it's matching the core with the
wrong binary.
I'm sure there's a way to switch binaries within gdb, but I don't know
it offhand. I'd just start a new gdb like:
gdb git-upload-pack 32433
-Peff
next prev parent reply other threads:[~2019-03-28 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 0:49 Puzzling Git backtrace Bryan Turner
2019-03-28 1:49 ` Jeff King [this message]
2019-03-28 2:59 ` Bryan Turner
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=20190328014957.GA7887@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=bturner@atlassian.com \
--cc=git@vger.kernel.org \
/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).