From: "Heinrich Nirschl" <heinrich.nirschl@gmail.com>
To: "Alex Bennee" <kernel-hacker@bennee.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn crashing perl
Date: Sun, 19 Oct 2008 08:39:35 +0200 [thread overview]
Message-ID: <394ab6ec0810182339j5f6cc1d6i6693ef878b9be12e@mail.gmail.com> (raw)
In-Reply-To: <b2cdc9f30810181500u357ce6e2tb8bef4fd559e89d3@mail.gmail.com>
On Sun, Oct 19, 2008 at 12:00 AM, Alex Bennee <kernel-hacker@bennee.com> wrote:
> Looks similar. libapr certainly seems to be breaking something:
>
>
> Core was generated by `/usr/bin/perl
> /home/alex/src/git.git/install/libexec/git-core/git-svn fetch --f'.
> Program terminated with signal 11, Segmentation fault.
> #0 0x00007fd0d813c370 in ?? ()
> (gdb) bt
> #0 0x00007fd0d813c370 in ?? ()
> #1 0x00007fd0d9a52a5d in ?? () from /usr/lib/libapr-1.so.0
> #2 0x00007fd0d9a53d9a in ?? () from /usr/lib/libapr-1.so.0
> #3 0x00007fd0d9a54003 in ?? () from /usr/lib/libapr-1.so.0
> #4 0x00007fd0d9a53d88 in ?? () from /usr/lib/libapr-1.so.0
> #5 0x00007fd0d9a54003 in ?? () from /usr/lib/libapr-1.so.0
> #6 0x00007fd0d9a540f3 in apr_pool_terminate () from /usr/lib/libapr-1.so.0
> #7 0x00007fd0db1c6e83 in _wrap_apr_terminate () from
> /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux/auto/SVN/_Core/_Core.so
> #8 0x000000000047dbab in Perl_pp_entersub ()
> #9 0x00000000004677fa in Perl_runops_debug ()
> #10 0x0000000000425ae8 in Perl_call_sv ()
> #11 0x0000000000425faa in Perl_call_list ()
> #12 0x000000000042a0e8 in perl_destruct ()
> #13 0x0000000000422238 in main ()
I found another bug report that seems to be related
http://bugs.gentoo.org/show_bug.cgi?id=223747
There is a workaround mentioned: disable runtime-module-search when
building subversion.
prev parent reply other threads:[~2008-10-19 6:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 13:42 git-svn crashing perl Alex Bennee
2008-10-18 16:05 ` Heinrich Nirschl
2008-10-18 22:00 ` Alex Bennee
2008-10-19 6:39 ` Heinrich Nirschl [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=394ab6ec0810182339j5f6cc1d6i6693ef878b9be12e@mail.gmail.com \
--to=heinrich.nirschl@gmail.com \
--cc=git@vger.kernel.org \
--cc=kernel-hacker@bennee.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.
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 NNTP newsgroup(s).