From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Szőts Ákos" <szotsaki@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git svn 2.26.0 segfault on fetch
Date: Fri, 27 Mar 2020 21:26:56 +0000 [thread overview]
Message-ID: <20200327212656.GM6499@camp.crustytoothpaste.net> (raw)
In-Reply-To: <CAAr69zbzX=ihOQLZRELWHaC42vs=XtNGkuJ+WhzeWaokPNcfAA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3579 bytes --]
On 2020-03-27 at 16:36:56, Szőts Ákos wrote:
> Dear list,
>
> When I use a "git svn fetch" on my git-SVN repository it dies with
> "error: git-svn died of signal 11".
>
> I tried to get a coredump or attach GDB to it but as I see in strace
> there are signal handlers attached to INT, HUP, TERM, QUIT, and PIPE
> and possibly because of them no coredumps are generated even with
> unlimited "-c" and also possibly because of this GDB doesn't stop on
> SIGSEGV.
Git uses the Subversion Perl bindings and git-svn is written entirely in
Perl. While it's possible we've broken something, it's probably a
little more likely that the Subversion Perl bindings on your system are
a little broken and that's what's causing the issue.
What operating system are you using?
> What I could do still with turned off ASLR is to run Valgrind with
> children tracking. It gave the following results:
>
> Warning: invalid file descriptor -1 in syscall close()
> Invalid read of size 4
> at 0x9B1A82C: UnknownInlinedFun (atomic_base.h:419)
> by 0x9B1A82C: UnknownInlinedFun (qatomic_cxx11.h:239)
> by 0x9B1A82C: UnknownInlinedFun (qbasicatomic.h:107)
> by 0x9B1A82C: UnknownInlinedFun (qrefcount.h:66)
> by 0x9B1A82C: UnknownInlinedFun (qstring.h:1263)
> by 0x9B1A82C: UnknownInlinedFun (kaboutdata.cpp:460)
> by 0x9B1A82C: KAboutData::~KAboutData() (kaboutdata.cpp:583)
> by 0x9B1AADC: (anonymous
> namespace)::Q_QGS_s_registry::innerFunction()::Holder::~Holder()
> (kaboutdata.cpp:1041)
> by 0x4A63706: __run_exit_handlers (exit.c:108)
> by 0x4A638BB: exit (exit.c:139)
> by 0x154465: main (perlmain.c:171)
> Address 0x80cf1c0 is not stack'd, malloc'd or (recently) free'd
This looks like you're loading something with Qt. Are you using the
Subversion KWallet integration? Does disabling it make things work?
> Process terminating with default action of signal 11 (SIGSEGV): dumping core
> Access not within mapped region at address 0x80CF1C0
> at 0x9B1A82C: UnknownInlinedFun (atomic_base.h:419)
> by 0x9B1A82C: UnknownInlinedFun (qatomic_cxx11.h:239)
> by 0x9B1A82C: UnknownInlinedFun (qbasicatomic.h:107)
> by 0x9B1A82C: UnknownInlinedFun (qrefcount.h:66)
> by 0x9B1A82C: UnknownInlinedFun (qstring.h:1263)
> by 0x9B1A82C: UnknownInlinedFun (kaboutdata.cpp:460)
> by 0x9B1A82C: KAboutData::~KAboutData() (kaboutdata.cpp:583)
> by 0x9B1AADC: (anonymous
> namespace)::Q_QGS_s_registry::innerFunction()::Holder::~Holder()
> (kaboutdata.cpp:1041)
> by 0x4A63706: __run_exit_handlers (exit.c:108)
> by 0x4A638BB: exit (exit.c:139)
> by 0x154465: main (perlmain.c:171)
> If you believe this happened as a result of a stack
> overflow in your program's main thread (unlikely but
> possible), you can try to increase the size of the
> main thread stack using the --main-stacksize= flag.
> The main thread stack size used in this run was 8388608.
>
> During stracing I found this line around the SIGSEGV:
> close(-1) = -1 EBADF
>
> If you could tell me how it's possible to attach GDB onto it, I'd be
> glad to provide you some backtraces as well.
You'd need to run something like the following:
gdb --args /usr/bin/perl /usr/lib/git-core/git-svn <ARGS>
Note that I don't use git-svn and remember next to nothing about using
Subversion, so hopefully any information you provide makes sense to
someone more familiar with git-svn than I.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2020-03-27 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 16:36 git svn 2.26.0 segfault on fetch Szőts Ákos
2020-03-27 21:26 ` brian m. carlson [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=20200327212656.GM6499@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=szotsaki@gmail.com \
/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).