Hi,
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).
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.
d) even with a correct stack trace and all local variable values
available, it still misses some contextual information. For serf that
means proxy config, authentication types etc.
So, is there anything that can be done to solve this?
I'm looking now at issue 31544 libsvn_tsvn!serf__open_connections
(which apparently still happens in TSVN 1.8.2). What I need to get a
better understanding of the problem is:
- url of the server
- if a proxy server is configured, with or without user name and
password (basic/digest vs NTLM/Negotiate authn)
- the exact line of code where it fails
- all function parameter variables in the stack trace
- all local variable values
- the user's local ip address, proxy ip address (ipv4 vs ipv6)
- amount of memory in use, amount of memory available
I suppose if I can get issues b and c solved, I'll have most of the
required info since I get the relevant context from the svn ra_session
and serf serf_session_t objects.
So, question 1: Is it possible to read those minidump files and get
correct crash location and all the relevant variable values?
Question 2: if this is not possible, can you log certain information
and send it with the crash report to crash-server.com were I can read
it?
Alternative 1: I seem to have no problem reading variables in the tsvn
part of a stack trace, so a global 'debug' object with some values or
some lines of logging would be helpful here.
Alternative 2: there was a request on the svn mailing list to be able
to enable serf logging at runtime. This hasn't been implemented yet,
but when it is, It'd be nice of tsvn could upload warning and error
log lines together with the crash reports.
thanks,
Lieven
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3063680
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-08-31 13:54:11 CEST