Recent changes to TrackingErrors

TrackingErrors modified by jura

jura — Sat, 26 Mar 2016 21:24:26 -0000

--- v3
+++ v4
@@ -1,5 +1,5 @@
 Often it is not possible to find and fix an error, if a user just reports: "I have the error X, when I try to do Y". 
-Also release versions of Transmission Remote GUI do not include debug information  to produce useful stack traces with source code line numbers.
+Release versions of Transmission Remote GUI do not include debug information to produce useful stack traces with source code line numbers.

 It is needed to build a debug version of the program to provude such information.

TrackingErrors modified by jura

jura — Sat, 26 Mar 2016 21:23:35 -0000

--- v2
+++ v3
@@ -1,6 +1,7 @@
 Often it is not possible to find and fix an error, if a user just reports: "I have the error X, when I try to do Y". 
+Also release versions of Transmission Remote GUI do not include debug information  to produce useful stack traces with source code line numbers.

-It is needed to provide more details, like call stack information with line numbers. 
+It is needed to build a debug version of the program to provude such information.

 To do that:

TrackingErrors modified by jura

jura — Sat, 26 Mar 2016 21:18:38 -0000

--- v1
+++ v2
@@ -1,4 +1,4 @@
-Often it is not possible to find and fix a error, if a user just reports: "I have the error X, when I try to do Y". 
+Often it is not possible to find and fix an error, if a user just reports: "I have the error X, when I try to do Y".

 It is needed to provide more details, like call stack information with line numbers.

Discussion for TrackingErrors page

Anonymous — Fri, 01 May 2015 20:26:12 -0000

Originally posted by: h0rnytoad1

seems overly complicated just to send a log file to the devs.

Here's an idea, add something like "save log to disc..." in the gui and ask us for logs when needed. gui can then copy the log from the nas or server locally and we can just attach to a reply here on the site.

Seems much easier for everyone and there's more chance this way that people will get involved and actually send logs.

TrackingErrors modified by Anonymous

Anonymous — Fri, 01 May 2015 20:26:12 -0000

Often it is not possible to find and fix a error, if a user just reports: "I have the error X, when I try to do Y".

It is needed to provide more details, like call stack information with line numbers.

To do that:

Download and install FPC and Lazarus, download the transgui source code. See the Building wiki page to learn how to build the program.
Build the program using the following command: make clean debug
Run transgui and reproduce the error.
You should see a call stack information in the error message box. The call stack information has been copied to the clipboard.
Paste this call stack information to your bug report.