From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Subject: Re: svn segfault when using svn+ssh schema
Date: Sun, 08 Jan 2017 21:16:00 -0000 [thread overview]
Message-ID: <4aa633a9-96a6-ba7c-e638-314522d98abe@dronecode.org.uk> (raw)
In-Reply-To: <9a5a8d1d-2b71-522e-59a6-29ad915e2445@acm.org>
On 08/01/2017 20:45, David Rothenberger wrote:
> On 1/8/2017 6:12 AM, Sam Edge wrote:
[...]
>>
>> I've attached cygcheck & the segfault stackdump.
>>
>> I'm at a loss. Any ideas?
>
> [Cygwin subversion maintainer here.]
>
> Sorry, I have no further ideas. svn+ssh is working fine for me here
> using both Cygwin and Debian as the server. Debian is running Subversion
> 1.8.10.
>
> I personally lack the technical skills to decode the stack trace. Maybe
> someone else can. Alternatively, you could theoretically download the
The script at [1] shows how to do this. Unfortunately...
> $ stackdump2backtrace svn.stackdump
> 0x0000000180053d3f dll_list::populate_deps(dll*) dll_init.cc:271
> 0x0000000180053f9a dll_list::topsort() dll_init.cc:309
> 0x00000001800ab62d fork fork.cc:597
> 0x000000018011882b xc sigfe.s:43
> 0x00000003fa778644 xc ??:0
> 0x00000003ed275773 xc ??:0
> 0x00000003ed275e3d xc ??:0
> 0x00000003ed2d41f4 xc ??:0
> 0x00000003ed40fc0f xc ??:0
> 0x00000003ed41079e xc ??:0
> 0x00000003ed3f2d59 xc ??:0
> 0x00000003ed3f3320 xc ??:0
> 0x000000010040b9f9 svn_cl__list list-cmd.c:387
> 0x00000001004178fd sub_main svn.c:3042
> 0x000000010041b755 main svn.c:3126
> 0x0000000180047902 dll_crt0_1(void*) dcrt0.cc:1018
... this is a crash in the cygwin DLL.
Also unfortunately, the stackdump doesn't record the DLLs loaded and
their bases addresses, so we can only guess which one ended up at
0x00000003e0000000
> subversion debug package and reproduce the error in gdb to get a
> backtrace. Again, my C/gdb skills are rusty, so I can't provide any
> details about how to do that.
So see also [2] and note well the point about 'set cygwin-exceptions on'
[1] https://cygwin.com/ml/cygwin/2015-08/msg00311.html
[2] https://cygwin.com/faq.html#faq.programming.debugging-cygwin
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-01-08 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 14:12 Sam Edge
2017-01-08 20:45 ` David Rothenberger
2017-01-08 21:16 ` Jon Turney [this message]
2017-01-09 2:04 ` Eliot Moss
2017-01-09 19:08 ` Sam Edge
2017-01-16 20:07 ` Sam Edge
2017-01-16 20:26 ` Jon Turney
2017-01-16 22:22 ` Sam Edge
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=4aa633a9-96a6-ba7c-e638-314522d98abe@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).