On Sat, Aug 31, 2013 at 4:33 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 31.08.2013 13:49, Lieven Govaerts wrote:
>> I've been looking at the crash reports for TSVN on crash-server.com,
>> specifically those related to the serf library.
>> When analyzing the reports and associated dump files, I've often found
>> that not enough information was available to correctly assess the
>> context of when the issue occurred. The stack trace alone is not
>> sufficient, especially because:
>> a) the stack trace available directly on the website only shows function names
>> b) I've noticed in the detailed stack traces that Stefan Küng sends to
>> the svn-dev mailing list that the line numbers do not match with the
>> source code (there is an offset).
> If they have an offset, then most likely you don't use the exact same
> files. Or: the files have inconsistent EOLs and the debugger then
> calculates the line numbers wrong.
>> c) the minidump files that I've downloaded never had function
>> parameter or local variable values for code in the svn or serf
>> library, at least, the values were corrupt from the point where the
>> the code path entered the svn library.
>> Note: for analysing the 1.8.1 minidumps I've used the 1.8.1 symbol
>> files, so there shouldn't be a version mismatch involved.
> You should use the exact debug symbols I used for the build. Those debug
> symbols are stored on the crash-server.com server.
I noticed that you're not using "/Oy-" (Frame-Pointer Omission) 
when building serf and Subversion. This option used for default
Subversion/serf builds. Without this option optimizing compiler
suppresses creation of frame pointers on the call stack. And this
makes debugging crash dumps very difficult. May be it worth to add
"/Oy-" after "/O2" to disable frame-pointer omission to make debugging
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-09-03 10:14:18 CEST