|
From: Jaroslaw B. <jar...@gm...> - 2008-02-04 13:59:55
|
Hi, I'm trying to run Valgrind memcheck with following command line: $valgrind --leak-check=full --leak-resolution=high --show-reachable=yes --xml=$xml --track-fds=yes --db-attach=yes --run-libc-freeres=yes <my_program> As far as I understood for documentation --db-attach=yes should call gdb upon encountering an error. Hovever, Valgrind just prints out the errors (deliberately made in test program) and terminates. I am using Valgrind 3.3.0 from source tarball and gdb 6.7 on SUSE 10.1. Is there any way to remedy this situation? Or am I doing something wrong? Regards, Jaroslaw |
|
From: David L <id...@gm...> - 2008-02-06 19:35:02
|
On Mon, Feb 4, 2008 at 5:57 AM, Jaroslaw Baranowski < jar...@gm...> wrote: > Hi, > > I'm trying to run Valgrind memcheck with following command line: > > $valgrind --leak-check=full --leak-resolution=high > --show-reachable=yes --xml=$xml --track-fds=yes --db-attach=yes > --run-libc-freeres=yes <my_program> > > As far as I understood for documentation --db-attach=yes should call > gdb upon encountering an error. Hovever, Valgrind just prints out the > errors (deliberately made in test program) and terminates. > > I am using Valgrind 3.3.0 from source tarball and gdb 6.7 on SUSE 10.1. > > Is there any way to remedy this situation? Or am I doing something wrong? I also have had problems with db-attach: http://bugs.kde.org/show_bug.cgi?id=153879 Your symptoms sound a little different, but db-attach doesn't work for me either. David |
|
From: Jaroslaw B. <jar...@gm...> - 2008-02-07 11:18:51
|
On 2/6/08, David L <id...@gm...> wrote: > > > > On Mon, Feb 4, 2008 at 5:57 AM, Jaroslaw Baranowski > <jar...@gm...> wrote: > > Hi, > > > > I'm trying to run Valgrind memcheck with following command line: > > > > $valgrind --leak-check=full --leak-resolution=high > > --show-reachable=yes --xml=$xml --track-fds=yes --db-attach=yes > > --run-libc-freeres=yes <my_program> > > > > As far as I understood for documentation --db-attach=yes should call > > gdb upon encountering an error. Hovever, Valgrind just prints out the > > errors (deliberately made in test program) and terminates. > > > > I am using Valgrind 3.3.0 from source tarball and gdb 6.7 on SUSE 10.1. > > > > Is there any way to remedy this situation? Or am I doing something wrong? > I also have had problems with db-attach: > http://bugs.kde.org/show_bug.cgi?id=153879 > > Your symptoms sound a little different, but db-attach doesn't work for me > either. > > David > > Hi all, Thanks for your reply David. It could be actually two different problems, as you get a prompt for GDB to attach while there is none in my case. I have also tried this on openSUSE 10.3 x86-64 with following enviroment: Linux version 2.6.22.16-0.2-default (geeko@buildhost) (gcc version 4.2.1 (SUSE Linux)) #1 SMP 2008/02/01 19:36:55 UTC GDB is: GNU gdb 6.6.50.20070726-cvs and valgrind is: valgrind-3.3.0 Same as on my other machine - not even a prompt for gdb to attach to process. |