Problems discovered in branches/wxpropgrid

Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Problems discovered in branches/wxpropgrid_debugger SVN7712

(1/5) > >>

mmccarty12:
I apologize in advance if this is not to correct forum for these issues and would appreciate notification of the correct place.
Thank you.

While using newly installed Code::Blocks at obfuscated's suggestion
SVN7712
Path: .
URL: http://svn.berlios.de/svnroot/repos/codeblocks/branches/wxpropgrid_debugger
Repository Root: http://svn.berlios.de/svnroot/repos/codeblocks
Repository UUID: 98b59c6a-2706-0410-b7d6-d2fa1a1880c9
Revision: 7712
Node Kind: directory
Schedule: normal
Last Changed Author: tpetrov
Last Changed Rev: 7712
Last Changed Date: 2012-01-22 19:36:42 -0500 (Sun, 22 Jan 2012)

I ran into the following problems:

--- Code: ---Settings -> Debugger -> Common
Option: Display Debugger's Log
When checked does not display Debugger's Log in Logs & Others panel.
This was still the result after saving settings, exiting and restarting codeblocks

Right click on any tab in Logs & Others panel.
Popup menu -> Toggle -> Options do not include Debugger(Debug) as in my current working
Code::Blocks configuration (/trunk/SVN7494)

After compiling and installing Code::Blocks(DebugSVN7712), I loaded a project compiled while
using Code::Blocks(trunk/SVN7494).
I set a break point in the source code and ran the code using the Debug -> Start option.
The code did not break as expected. Was required to Build -> Clean/Debug -> Start before
a break would occur.
As a side note, the debugger did stop somewhere(there was no arrow indicator as usual) and
the buttons in the Debugger toolbar could be clicked on but no action occurred.
After starting the program with no breakpoints set, I attempted to add breakpoints.
The following is what was displayed in the Debug tab:

[quote]
[color=green][debug]Child process (pid:8988) doesn't exists
[debug]Code::Blocks is trying to interrupt process with pid: 8983; child pid: 8988 gdb pid: 8983

Continuing...
[/quote]
[/color]

--- End code ---

The above was displayed each time I attempted to add a breakpoint while the program was running.

I tried to use the Break Debugger option in the Debugger Toolbar and this was displayed in the
Debugger tab:

[debug]Child process (pid:8988) doesn't exists
[debug]Code::Blocks is trying to interrupt process with pid: 8983; child pid: 8988 gdb pid: 8983

Continuing...

After all of the above, I was not able to exit out of Debugging Mode. I was required to
use the System Monitor to kill the gdb/program processes.

Start Page info
svn build rev 7712 (2012-01-23 00:36:42) gcc 4.4.4 Linux/unicode - 64 bit

Running CentOS 5.7
Configured Code::Blocks with the following:
../configure --prefix=<non-default-path>/build --with-contrib-plugins=all,-NassiShneiderman,-byogames,-spellchecker CC=gcc44 CXX=g++44

Compilation went fine after removing NassiShneiderman and spellchecker options.

--- Code: ---gcc44 --v
Using built-in specs.
Target: x86_64-redhat-linux6E
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --disable-gnu-unique-object --enable-languages=c,c++,fortran --disable-libgcj --with-mpfr=/builddir/build/BUILD/gcc-4.4.4-20100726/obj-x86_64-redhat-linux6E/mpfr-install/ --with-ppl=/builddir/build/BUILD/gcc-4.4.4-20100726/obj-x86_64-redhat-linux6E/ppl-install --with-cloog=/builddir/build/BUILD/gcc-4.4.4-20100726/obj-x86_64-redhat-linux6E/cloog-install --with-tune=generic --with-arch_32=i586 --build=x86_64-redhat-linux6E
Thread model: posix
gcc version 4.4.4 20100726 (Red Hat 4.4.4-13) (GCC)

g++44 --v
Using built-in specs.
Target: x86_64-redhat-linux6E
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --disable-gnu-unique-object --enable-languages=c,c++,fortran --disable-libgcj --with-mpfr=/builddir/build/BUILD/gcc-4.4.4-20100726/obj-x86_64-redhat-linux6E/mpfr-install/ --with-ppl=/builddir/build/BUILD/gcc-4.4.4-20100726/obj-x86_64-redhat-linux6E/ppl-install --with-cloog=/builddir/build/BUILD/gcc-4.4.4-20100726/obj-x86_64-redhat-linux6E/cloog-install --with-tune=generic --with-arch_32=i586 --build=x86_64-redhat-linux6E
Thread model: posix

wx-config --selected-config
[color=blue]gtk2-unicode-release-2.8[/color]
wx-config --version
[color=blue]2.8.12[/color]
wx-config --cppflags
[color=blue]-I/usr/local/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__[/color]
wx-config --libs
[color=blue]-L/usr/local/lib -pthread -L/usr/lib64 -lwx_gtk2u-2.8 [/color]

--- End code ---

oBFusCATed:
Debugger's debug log was removed and the output of it was moved in the normal debug log using the [debug] prefix.
This was made, because too many people were having trouble finding/enabling the log and so they were wasting my time.
I guess, I have to rename the option, so it is more clear.

Can you paste the full log? Do you use some kind of forking?
If you use forking you'll have many problems, because C::B's current debugger plugin doesn't work well with forking debuggees.

p.s. please use code tags for long pastes.

mmccarty12:
oBFusCATed,

Thank you for your immediate reply.

--- Quote ---oBFusCATed:
Can you paste the full log? Do you use some kind of forking?
If you use forking you'll have many problems, because C::B's current debugger plugin doesn't work well with forking debuggees.
--- End quote ---

I am unsure what you are asking for here. If you can give me more details, I am sure I can give you what you are looking for with this problem.
In the program I was running during all of this, there is no forking.

--- Quote ---oBFusCATed:
p.s. please use code tags for long pastes.
--- End quote ---
Again, I am unsure what you are looking for here.

oBFusCATed:
Right click in the Debug tab and choose "Copy contents to clipboard", then paste the copied text in a new post between [ code ] [/ code ] (removing the spaces) and hit Post.

mmccarty12:

--- Code: ---Building to ensure sources are up-to-date
Selecting target:
Debug
Adding source dir: /scratch/mccarty/Dem3D/Dem3dPre/
Adding source dir: /scratch/mccarty/Dem3D/Dem3dPre/
Adding file: /scratch/mccarty/Dem3D/Dem3dPre/bin/Debug/Dem3dPreDebug-2012-01-24
Changing directory to: /scratch/mccarty/Dem3D/Dem3dPre/.

[debug]LD_LIBRARY_PATH=.:/opt/intel/Compiler/11.0/081/lib/intel64:/opt/intel/Compiler/11.0/081/mkl/lib/em64t:.:/philo/filesystems/maxwell/release/passage_flow/bin/LINUX/mpi/lib:/usr/lib:/usr/bin:/usr/lib/pkgconfig:/lib:/usr/local/lib/wx:/usr/local/lib:/scratch/mccarty/boost/build/lib:/usr/local/cuda/lib64
[debug]Command-line: /usr/bin/gdb -nx -fullname -quiet -args /scratch/mccarty/Dem3D/Dem3dPre/bin/Debug/Dem3dPreDebug-2012-01-24
[debug]Working dir : /scratch/mccarty/Dem3D/Dem3dPre

Starting debugger: /usr/bin/gdb -nx -fullname -quiet -args /scratch/mccarty/Dem3D/Dem3dPre/bin/Debug/Dem3dPreDebug-2012-01-24
done

[debug]Reading symbols from /scratch/mccarty/Dem3D/Dem3dPre/bin/Debug/Dem3dPreDebug-2012-01-24...
[debug]> set prompt >>>>>>cb_gdb:

Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints

[debug]done.
[debug](gdb) >>>>>>cb_gdb:
[debug]> show version
[debug]GNU gdb (GDB) 7.1
[debug]Copyright (C) 2010 Free Software Foundation, Inc.
[debug]License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
[debug]This is free software: you are free to change and redistribute it.
[debug]There is NO WARRANTY, to the extent permitted by law. Type "show copying"
[debug]and "show warranty" for details.
[debug]This GDB was configured as "x86_64-unknown-linux-gnu".
[debug]For bug reporting instructions, please see:
[debug]<http://www.gnu.org/software/gdb/bugs/>.
[debug]>>>>>>cb_gdb:
[debug]> set confirm off

Debugger name and version: GNU gdb (GDB) 7.1

[debug]>>>>>>cb_gdb:
[debug]> set width 0
[debug]>>>>>>cb_gdb:
[debug]> set height 0
[debug]>>>>>>cb_gdb:
[debug]> set breakpoint pending on
[debug]>>>>>>cb_gdb:
[debug]> set print asm-demangle on
[debug]>>>>>>cb_gdb:
[debug]> set unwindonsignal on
[debug]>>>>>>cb_gdb:
[debug]> set print elements 0
[debug]>>>>>>cb_gdb:
[debug]> set disassembly-flavor intel
[debug]>>>>>>cb_gdb:
[debug]> catch throw
[debug]Catchpoint 1 (throw)
[debug]>>>>>>cb_gdb:
[debug]> source /scratch/mccarty/codeblocksSVNDebug/wxpropgrid_debugger/build/share/codeblocks/scripts/stl-views-1.0.3.gdb
[debug]>>>>>>cb_gdb:
[debug]> directory /scratch/mccarty/Dem3D/Dem3dPre/
[debug]>>>>>>cb_gdb:
[debug]> run
[debug]warning: no loadable sections found in added symbol-file system-supplied DSO at 0x2aaaaaaab000
[debug][Thread debugging using libthread_db enabled]

--- End code ---

Program started with no breakpoints.

At this point I opened a source file and tried to add a breakpoint. The following message was displayed.

--- Code: ---[debug]Code::Blocks is trying to interrupt process with pid: 21664; child pid: 0 gdb pid: 21664

Continuing...

--- End code ---

After adding the break point with the above message displayed, I tried to open a file from within my program.
The following was displayed.

--- Code: ---[debug]Quit
[debug]>>>>>>cb_gdb

--- End code ---

I hope this is enough information.
The program is being developed on the above mentioned system using the wxWidgets-2.9.2 API.
The program runs fine with no problems when not trying to debug at run-time, meaning that if I set breakpoints before
starting the program it will break properly. However, I have run into situations where the program quits running if
I remove set breakpoints while the program is running. The program will lock up or it will crash abruptly.

Navigation

[0] Message Index

[#] Next page

Go to full version