On Wed, Mar 27, 2019 at 6:50 PM Jeff King <peff@xxxxxxxx> wrote: > > 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". Derp. Of course. Sorry, clearly it's been too long since I used C in anger! Thanks for taking the time to point out what should have been obvious, and for doing it so kindly! Bryan
