I just realized those are not the right debug files anyway. I'll try to dig them up.
Sent from my iPad
> On Jun 30, 2014, at 5:50 PM, Branko Čibej <brane_at_wandisco.com> wrote:
>
>> On 30.06.2014 22:41, Mark Phippard wrote:
>> I do not know how you can debug, but I can point you to PDB's for the binaries you are using.
>>
>> http://pkg.collab.net/build/windows/CollabNet_Subversion-Win32-Debug-1.8.9.47.zip
>>
>> Brane might know better how you can use these to get better info.
>
> Well, I've never done any debugging with JavaHL on Windows. But if you somehow manage to make those .pdb's available to the JVM -- I guess it should be enough to put them in the same directory as the relevant .dll's -- then at least the JVM crash report stack trace should give better info about what caused the crash.
>
> It would also be possible to attach a debugger to the Eclipse process then; but it'll have to be a native, not Java debugger, since the crash happens in native code.
>
> -- Brane
>
>>> On Mon, Jun 30, 2014 at 4:20 PM, Darly Senecal Baptiste <dsenecalb_at_gmail.com> wrote:
>>>
>>>>
>>>> This is a bit of a problem ... there's no debug information available for the native libraries, which makes it rather hard to tell what the problem might be.
>>>>
>>>>
>>>> Is the repository by any chance public, so that I could try to do a checkout using JavaHL within a debugger?
>>>>
>>>
>>> I don't think ... However, is there a way that I can debug it from Eclipse?
>
> --
> Branko Čibej | Director of Subversion
> WANdisco // Non-Stop Data
> e. brane_at_wandisco.com
Received on 2014-07-01 00:27:32 CEST