Debugger does not work
-
- CodeLite Guru
- Posts: 352
- Joined: Sun Nov 29, 2009 7:36 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Debugger does not work
Hi,
I use Codelite latest SVN (Selef compiled if you wish) but debugger have stopped working. I can start debugger but Next and other buttons don't work. I cannot then debug code. I don't know what went wrong!
I use Codelite latest SVN (Selef compiled if you wish) but debugger have stopped working. I can start debugger but Next and other buttons don't work. I cannot then debug code. I don't know what went wrong!
CodeLite 15.x
CodeLite is awesome, I just Love it!
-
- CodeLite Guru
- Posts: 352
- Joined: Sun Nov 29, 2009 7:36 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: Debugger does not work
I have uninstalled it and tried to install natty version but it doesn’t work also!
I forgot to add info:
Ubuntu Natty, wx29 (Compiled CL using 28 dev)
Thanks!
I forgot to add info:
Ubuntu Natty, wx29 (Compiled CL using 28 dev)
Thanks!
CodeLite 15.x
CodeLite is awesome, I just Love it!
-
- CodeLite Plugin
- Posts: 819
- Joined: Wed Sep 03, 2008 7:26 pm
- Contact:
Re: Debugger does not work
Hi,
It works for me, on natty using kde. Which DE/window manager are you using? If it's 'unity', does trying 'classic' make a difference? Is it just the toolbar that doesn't work, or do the menuitems and shortcut keys fail too?
I assume you have gdb installed, and are trying to debug a 'debug' build of your app, built against a debug build of wxGTK. What do you see in the output pane? And what do you see there after ticking 'Enable debugger full logging'?
Regards,
David
It works for me, on natty using kde. Which DE/window manager are you using? If it's 'unity', does trying 'classic' make a difference? Is it just the toolbar that doesn't work, or do the menuitems and shortcut keys fail too?
I assume you have gdb installed, and are trying to debug a 'debug' build of your app, built against a debug build of wxGTK. What do you see in the output pane? And what do you see there after ticking 'Enable debugger full logging'?
Regards,
David
-
- CodeLite Guru
- Posts: 352
- Joined: Sun Nov 29, 2009 7:36 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: Debugger does not work
Hi!DavidGH wrote:Hi,
I use Gnome/Unity. I don't know when it stopped. I just cannot debug, even close files I have openedDavidGH wrote:It works for me, on natty using kde. Which DE/window manager are you using? If it's 'unity', does trying 'classic' make a difference? Is it just the toolbar that doesn't work, or do the menuitems and shortcut keys fail too?
gdb -vDavidGH wrote:I assume you have gdb installed, and are trying to debug a 'debug' build of your app, built against a debug build of wxGTK. What do you see in the output pane? And what do you see there after ticking 'Enable debugger full logging'?
Regards,
David
GNU gdb (Ubuntu/Linaro 7.2-1ubuntu11) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
I'm confused!
Re installing, delete all SVN and checkout and compile....nothing works. Compiling goes fine!
CodeLite 15.x
CodeLite is awesome, I just Love it!
-
- CodeLite Plugin
- Posts: 819
- Joined: Wed Sep 03, 2008 7:26 pm
- Contact:
Re: Debugger does not work
I just tested CodeLite on unity; the only unusual thing about the installation is that it's a virtualbox guest. Debugging worked as it should :/ . Did you try changing from unity to 'classic'?I use Gnome/Unity
Please tick 'Enable debugger full logging' and report what is output in a debug session. Please try using the menuitems in the Debug menu e.g. 'Pause debugger' and 'Next'. Please try the keyboard shortcuts for 'Next' etc.
- eranif
- CodeLite Plugin
- Posts: 6375
- Joined: Wed Feb 06, 2008 9:29 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: Debugger does not work
I recently upgraded to Unity as well, no problems here.
Please post the complete debugger log:
http://codelite.org/forum/viewtopic.php?f=3&t=804#p3562
Eran
Please post the complete debugger log:
http://codelite.org/forum/viewtopic.php?f=3&t=804#p3562
Eran
Make sure you have read the HOW TO POST thread
-
- CodeLite Guru
- Posts: 352
- Joined: Sun Nov 29, 2009 7:36 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: Debugger does not work
cannot see where to get the logs. Already enabled them in settings!
CodeLite 15.x
CodeLite is awesome, I just Love it!
-
- CodeLite Guru
- Posts: 352
- Joined: Sun Nov 29, 2009 7:36 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: Debugger does not work
Installed previous version 2.8 from Ubuntu repo, run full debug logging and got this:
Using gdbinit file: /home/stefano/.gdbinit
Current working dir: /home/stefano/Documents/developer/projects/HosannaNeno/CoreApplication
Launching gdb from : ../application/
Starting debugger : gdb --tty=/dev/pts/3 --interpreter=mi "./HosannaNeno"
Debug session started successfully!
GNU gdb (Ubuntu/Linaro 7.2-1ubuntu11) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type "show copying"\nand "show warranty" for details.
This GDB was configured as "i686-linux-gnu".\nFor bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/stefano/Documents/developer/projects/HosannaNeno/application/HosannaNeno...
done.
Debuggee process ID: 30038
Successfully set breakpoint 1 at: /home/stefano/Documents/developer/projects/HosannaNeno/CoreApplication/bibleviewer.cpp:1154
Continuing...
[Thread debugging using libthread_db enabled]
[New Thread 0xb7ba8b70 (LWP 30044)]
[New Thread 0xb71ffb70 (LWP 30045)]
[New Thread 0xb69feb70 (LWP 30046)]
[Thread 0xb69feb70 (LWP 30046) exited]
[Thread 0xb7ba8b70 (LWP 30044) exited]
/build/buildd/gdb-7.2/gdb/findvar.c:427: internal-error: read_var_value: Assertion `frame' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session?
(y or n)
Please answer y or n.
/build/buildd/gdb-7.2/gdb/findvar.c:427: internal-error: read_var_value: Assertion `frame' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session?
(y or n)
Please answer y or n.
/build/buildd/gdb-7.2/gdb/findvar.c:427: internal-error: read_var_value: Assertion `frame' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session?
(y or n)
DEBUG>>00000011-exec-next
DEBUG>>00000011-exec-next
DEBUG>>~"Please answer y or n.\n"
Please answer y or n.
DEBUG>>~"/build/buildd/gdb-7.2/gdb/findvar.c:427: internal-error: read_var_value: Assertion `frame' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session? "
/build/buildd/gdb-7.2/gdb/findvar.c:427: internal-error: read_var_value: Assertion `frame' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session?
DEBUG>>~"(y or n) "
(y or n)
DEBUG>>00000012-exec-next
DEBUG>>00000012-exec-next
DEBUG>>~"Please answer y or n.\n"
Please answer y or n.
DEBUG>>~"/build/buildd/gdb-7.2/gdb/findvar.c:427: internal-error: read_var_value: Assertion `frame' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session? "
/build/buildd/gdb-7.2/gdb/findvar.c:427: internal-error: read_var_value: Assertion `frame' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session?
DEBUG>>~"(y or n) "
(y or n)
DEBUG>>00000013-exec-next
DEBUG>>00000013-exec-next
DEBUG>>~"Please answer y or n.\n"
Please answer y or n.
DEBUG>>~"/build/buildd/gdb-7.2/gdb/findvar.c:427: internal-error: read_var_value: Assertion `frame' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session? "
/build/buildd/gdb-7.2/gdb/findvar.c:427: internal-error: read_var_value: Assertion `frame' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session?
DEBUG>>~"(y or n) "
(y or n)
DEBUG>>00000014-var-create - @ "tkr.GetNextToken"
DEBUG>>00000014-var-create - @ "tkr.GetNextToken"
DEBUG>>~"Please answer y or n.\n"
Please answer y or n.
DEBUG>>~"/build/buildd/gdb-7.2/gdb/findvar.c:427: internal-error: read_var_value: Assertion `frame' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session? "
/build/buildd/gdb-7.2/gdb/findvar.c:427: internal-error: read_var_value: Assertion `frame' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session?
DEBUG>>~"(y or n) "
(y or n)
DEBUG>>00000015-exec-next
DEBUG>>00000015-exec-next
DEBUG>>~"Please answer y or n.\n"
Please answer y or n.
DEBUG>>~"/build/buildd/gdb-7.2/gdb/findvar.c:427: internal-error: read_var_value: Assertion `frame' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session? "
/build/buildd/gdb-7.2/gdb/findvar.c:427: internal-error: read_var_value: Assertion `frame' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session?
DEBUG>>~"(y or n) "
(y or n)
CodeLite 15.x
CodeLite is awesome, I just Love it!
-
- CodeLite Plugin
- Posts: 819
- Joined: Wed Sep 03, 2008 7:26 pm
- Contact:
Re: Debugger does not work
That's probably being caused by a gdb bug that's present in 7.2 and other recent gdb versions, and is known to affect wx programs.
I suggest that you build gdb from svn; I've not had this problem since doing so.
I suggest that you build gdb from svn; I've not had this problem since doing so.
-
- CodeLite Guru
- Posts: 352
- Joined: Sun Nov 29, 2009 7:36 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: Debugger does not work
Hi,DavidGH wrote:That's probably being caused by a gdb bug that's present in 7.2 and other recent gdb versions, and is known to affect wx programs.
I suggest that you build gdb from svn; I've not had this problem since doing so.
SVN is no where to be found yet. I think they are still into cvs. Even that, Cvsed code didn't compile. so after few google shots I found latest snapshots here and ./configure && make && sudo make install worked great.
Now debugger is working as normal.
Great thanks to Dave and everybody else tried to help
CodeLite 15.x
CodeLite is awesome, I just Love it!