writes:
> Can you please confirm that the downgrading from v2 to v1 is away now?
Yes, that is v2.
--
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
> -Ursprüngliche Nachricht-
> Von: Philip Martin [mailto:philip.mar...@wandisco.com]
> Gesendet: Freitag, 9. Januar 2015 16:25
> An: Viret Pierre, PF54
> Cc: users@subversion.apache.org
> Betreff: Re: AW: AW: AW: AW: AW: AW: Segmentation Fault with SVN Client
writes:
> Question: do you know when the patch for the header field name
> case-sensitiveness will be delivered? Is it planned for 1.8.12 SVN
> client?
It's approved for 1.8.12, see:
http://svn.apache.org/repos/asf/subversion/branches/1.8.x/STATUS
--
Philip Martin | Subversion Committer
WAN
> -Ursprüngliche Nachricht-
> Von: Philip Martin [mailto:philip.mar...@wandisco.com]
> Gesendet: Freitag, 9. Januar 2015 12:19
> An: Viret Pierre, PF54
> Cc: users@subversion.apache.org
> Betreff: Re: AW: AW: AW: AW: AW: Segmentation Fault with SVN Client related to
&
writes:
> Yes you are right, I have not looked at the wireshark output good
> enough! Unfortunately I cannot change it in our HttpProxy: this
> change of the case of the header keys is performed by the underlying
> HTTP Layer in java and not by our own code. I think the reason for
> this is that
;> Betreff: Re: AW: AW: Segmentation Fault with SVN Client related to serf
>>
>> writes:
>>
>>> You asked for the whole sequence of request, here is the whole tracing
>>> of our proxy: I hope this helps. But as already said: the svn client
>>> does not c
> -Ursprüngliche Nachricht-
> Von: Philip Martin [mailto:philip.mar...@wandisco.com]
> Gesendet: Freitag, 9. Januar 2015 10:48
> An: Viret Pierre, PF54
> Cc: users@subversion.apache.org
> Betreff: Re: AW: AW: AW: AW: Segmentation Fault with SVN Client related to
>
writes:
> I have captured the http traffic, you will find it in the attachment
> crash_http_capture.pcap. The debugging output of the HttpProxy is in
> the attachment crash_http.txt, it differs from the output when using
> https. I had to switch from https to http for this. Please note that
> th
> -Ursprüngliche Nachricht-
> Von: Philip Martin [mailto:philip.mar...@wandisco.com]
> Gesendet: Mittwoch, 7. Januar 2015 14:51
> An: Viret Pierre, PF54
> Cc: users@subversion.apache.org
> Betreff: Re: AW: AW: Segmentation Fault with SVN Client related to serf
>
> -Ursprüngliche Nachricht-
> Von: Philip Martin [mailto:philip.mar...@wandisco.com]
> Gesendet: Donnerstag, 8. Januar 2015 14:34
> An: Viret Pierre, PF54
> Cc: users@subversion.apache.org
> Betreff: Re: AW: AW: AW: Segmentation Fault with SVN Client related to serf
Philip Martin writes:
> I can't reproduce this against a standard server.
I think I have worked it out. There was an error in my script: one of
the XML response lines was missing a '\n' and this originally caused the
client to report the HTTP response as too short, so I "fixed" it by
added a tr
Philip Martin writes:
> I've converted your trace into a Python script to implement a server
> that behaves like yours.
I may have reproduced the problem. If I remove the 'Connection: close'
headers and continue to force v1 I can get the client to crash using the
dummy server. I suppose that m
writes:
> The status line is not blocked. The debugging message means that we
> have got an header with a null key and with the status line as value:
> in this case the header is not added to the request sent back to the
> client. This seems to be common that some HTTP Implementations return
> su
> -Ursprüngliche Nachricht-
> Von: Philip Martin [mailto:philip.mar...@wandisco.com]
> Gesendet: Mittwoch, 7. Januar 2015 14:51
> An: Viret Pierre, PF54
> Cc: users@subversion.apache.org
> Betreff: Re: AW: AW: Segmentation Fault with SVN Client related to serf
>
writes:
> You asked for the whole sequence of request, here is the whole tracing
> of our proxy: I hope this helps. But as already said: the svn client
> does not crash always but 30% of the times we execute exactly the same
> ls command.
This is a bit confusing:
2015-01-06 15:43:24,260 DEBUG
> -Ursprüngliche Nachricht-
> Von: Stefan Sperling [mailto:s...@elego.de]
> Gesendet: Dienstag, 6. Januar 2015 15:59
> An: Philip Martin
> Cc: Viret Pierre, PF54; users@subversion.apache.org
> Betreff: Re: AW: Segmentation Fault with SVN Client related to serf
>
&
On Tue, Jan 06, 2015 at 02:01:52PM +, Philip Martin wrote:
> Typically the client will first send an OPTIONS request and get back a
> 401 or a 200. The client will then send further OPTIONS and PROPFIND
> requests. Can you identify which request and response is causing the
> crash? Also whic
> -Ursprüngliche Nachricht-
> Von: Philip Martin [mailto:philip.mar...@wandisco.com]
> Gesendet: Dienstag, 6. Januar 2015 15:02
> An: Viret Pierre, PF54
> Cc: users@subversion.apache.org
> Betreff: Re: AW: Segmentation Fault with SVN Client related to serf
>
[...]
On Tue, Jan 06, 2015 at 02:01:52PM +, Philip Martin wrote:
> The crash is happening in the code that parses the status line,
> i.e. when handling something like
>
> HTTP/1.1 200 OK
>
> or
>
> HTTP/1.1 207 Multi-Status
>
> or
>
> HTTP/1.1 401 Authorization Required
> Breakpoint 1,
writes:
> Here a description of the architecture we are using:
> - a http-proxy is running on 127.0.0.1:7771 which builds a secure
> https tunnel to a special reverse proxy, using a certificate from a
> smart-card
> - the reverse proxy then connects to the apache server used as
> subversion
> -Ursprüngliche Nachricht-
> Von: Philip Martin [mailto:philip.mar...@wandisco.com]
> Gesendet: Dienstag, 6. Januar 2015 12:49
> An: Viret Pierre, PF54
> Cc: users@subversion.apache.org
> Betreff: Re: Segmentation Fault with SVN Client related to serf
>
> wri
writes:
> viretp@mwbox:~$ svn ls https://127.0.0.1:7771/svn/t_sponis_testrepo
> Segmentation fault
>
> In /var/log/syslog:
> Jan 5 14:31:23 mwbox kernel: [14750.072747] svn[21822]: segfault at
> 7f3733f39000 ip 7f37328ae3cf sp 7fff9e3df468 error 7 in
> libc-2.13.so[7f373278a000+182000]
Hello
We have following problem with the SVN native clients in our environment: the
client crashes with a memory access violation error while executing an "ls"
command. We have reproduced the error on debian with SVN 1.8.10 and on Windows
with the latest SVN 1.8.11. With older versions of SVN c
23 matches
Mail list logo
