gdb debugging is locked

[Michael Stahl]

On 23.06.2015 16:40, marius adrian popa wrote:
> I started debugging the gist at the end of bug
> #72987 https://bugs.documentfoundation.org/show_bug.cgi?id=72987#c10
> 
> export DEBUGCPPUNIT=TRUE
> export CPPUNITTRACE="gdb --args"
> export VALGRIND=memcheck

you're supposed to set *one* of these variables, not all of them.

> make CppunitTest_dbaccess_firebird_test
> make -j 4 -rs -f /home/mariuz/work/libo/Makefile.gbuild
> CppunitTest_dbaccess_firebird_test
> 
> Seems that gdb debugging is locked (nothing happens)
> 
> 
> cat /proc/4198/cmdline 
> gdb-nx-exadd-auto-load-safe-path
> /home/mariuz/work/libo/instdir--command=/home/mariuz/work/libo/solenv/bin/gdbtrycatchtrace-stdout-return-child-result--argsvalgrind--tool=memcheck--num-callers=50--error-exitcode=1--trace-children=yes--trace-children-skip=*/java,*/gij/home/mariuz/work/libo/workdir/LinkTarget/Executable/cppunittester/home/mariuz/work/libo/workdir/LinkTarget/CppunitTest/libtest_dbaccess_firebird_test.so--headless-env:BRAND_BASE_DIR....

you're starting valgrind inside of gdb - it's not surprising that
doesn't work :)