Re: segfault with new conflict resolver

2017-01-30 Thread Stefan Kueng
On 28.01.2017 15:38, Stefan Sperling wrote: On Sat, Jan 28, 2017 at 01:47:03PM +0100, Stefan Sperling wrote: On Sat, Jan 28, 2017 at 01:31:46PM +0100, Stefan Kueng wrote: Hi, trying out the new conflict resolver. Ran into a segfault on my first try: Thank you! I will fix this ASAP. Shoul

Re: segfault with new conflict resolver

2017-01-28 Thread Stefan Sperling
On Sat, Jan 28, 2017 at 01:47:03PM +0100, Stefan Sperling wrote: > On Sat, Jan 28, 2017 at 01:31:46PM +0100, Stefan Kueng wrote: > > Hi, > > > > trying out the new conflict resolver. Ran into a segfault on my first try: > > Thank you! I will fix this ASAP. Should be fixed by r1780702.

Re: segfault with new conflict resolver

2017-01-28 Thread Stefan Sperling
On Sat, Jan 28, 2017 at 01:31:46PM +0100, Stefan Kueng wrote: > Hi, > > trying out the new conflict resolver. Ran into a segfault on my first try: Thank you! I will fix this ASAP. > libsvn_client\conflicts.c, function find_modified_rev(): > > if there is no author for a commit, then we get a s

segfault with new conflict resolver

2017-01-28 Thread Stefan Kueng
Hi, trying out the new conflict resolver. Ran into a segfault on my first try: libsvn_client\conflicts.c, function find_modified_rev(): if there is no author for a commit, then we get a segfault here: /* No paths were changed in this revision. Nothing to do. */ if (! log_entry->changed_pa