On Wednesday, January 31, 2018 at 11:20:04 PM UTC+1, Julian Foad wrote:
>
> ...
> \path\to\procdump64.exe -accepteula tortoiseproc
>
>
If you're only using it like this, there's a much easier way (on Win10 at
least):
* Open the task manager
* right-click on the tortoiseproc.exe process (in details view)
* select "create dump" (or something like this, on my system it's
"Abbilddatei erstellen")
> It should display something like:
>
> ProcDump v9.0 - Sysinternals process dump utility
> [...]
> [20:35:50] Dump 1 initiated:
> C:\...\TortoiseProc.exe_180131_203550.dmp
> [20:35:51] Dump 1 complete: 4 MB written in 0.2 seconds
> [20:35:51] Dump count reached.
>
> 5. Find the file that ProcDump saved
> ('C:\...\TortoiseProc.exe_180131_203550.dmp' in this example) and send
> it to the developer who is going to debug the issue.
>
>
> Do you think it is worth adding this info to the FAQ, round about here:
> https://tortoisesvn.net/faq.html#debug ?
>
>
Usually, if TSVN crashes the crash dumps are uploaded to drdump.com.
But if you think this would be helpful, we can of course do that.
> Then I attempted to test the above recipe, but with no success. This is
> how:
>
> I inserted "SVN_ERR_ASSERT_NO_RETURN(0);" at the beginning of
> svn_client_merge_peg5() in my debug build of libsvn_tsvn.dll. I used the
> trick of running TortoiseMerge in debug mode, opening its file-select
> dialog, then invoking TSVN from the context menu in there to access my
> debug build of TortoiseSVN. I clicked through TortoiseSVN's 'Merge...',
> got a dialog showing my injected assertion failure, saved the process
> dump, loaded that dump file into Visual Studio which showed a "mini dump
> summary", configured the symbols path, chose the action "Debug with
> Native Only", and looked at the stack trace shown.
>
>
Why don't you just start TortoiseProc in debug mode with the right command
line parameters? There's no need to go through TMerge, fileopen,
shellextension, tortoisproc - just debug TortoiseProc directly!
Right-click on the TortoiseProc project in VisualStudio, "Properties". Then
under Debugging->Command Arguments enter e.g.
/command:merge /path:"path/to/wc"
If you need to know the right parameters, go to the settings dialog,
Advanced, set the "Debug" to true. That will make TSVN show a dialog on
start showing the command line it was started with.
> The stack trace shown only contained TortoiseProc.exe entries. The other
> slots were just showing "[External Code]".
>
>
Under Debug->Options, (Options dialog->Debugging->General) in VS:
find the entry "Enable just my code" and uncheck it.
Also "Enable source server support" will help.
You can also right-click on the entry "[External Code]" and from the
context menu chose "Load symbols" - that will force the loading of the
debug symbols for those "external" codes.
Stefan
--
You received this message because you are subscribed to the Google Groups
"TortoiseSVN-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tortoisesvn-dev/a54ccb78-a7e9-49c7-9774-f01ccafee5ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
