From: Dan S. <dan...@go...> - 2012-05-31 18:41:51
|
On 31 May 2012 01:42, Philippe Waroquiers <phi...@sk...> wrote: > On Thu, 2012-05-31 at 01:17 +0200, Roland Mainz wrote: > >> IMO it would be nice to print the address of the "Invalid read" in >> line 1 and give the address of the object being affected (i.e. 'global >> array "x1_numbuff"' in this case). I would've saved us a lot of >> digging today... > If you need more info about an error context, you can always use > the Valgrind gdbserver : when the error is reported, you > have full access to all the variables etc. Philippe, the use of gdbserver should be optional, right? The output of exp-sgcheck is currently not enough to glance where the problem happens so you have to use gdb *everytimes*. This should not be required. |