Bug 83

Summary: Remove experimental status from gdb integration
Product: [Yocto Project Subprojects] Anjuta Plugin Reporter: Joshua Lock - Disabled <josh>
Component: anjuta-pluginAssignee: Joshua Lock - Disabled <josh>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: High CC: gary, liping.ke, sgw, yongkang.you, yp.ap.watcher, yp.watcher
Version: 0.9   
Target Milestone: 0.9 M1   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Program Management Documentation change: ---

Description Joshua Lock - Disabled 2010-02-23 17:29:21 UTC
This is a pretty killer feature but is disabled by default (requiring a configure flag to enable it at build time).

We should make sure this is rock solid and enable by default.
Comment 1 Joshua Lock - Disabled 2010-04-07 10:41:57 UTC
We'll need to thoroughly test and fix up issues such as those noted on the list by Gary:

* The local connection to GDB seems to have trouble with the anjuta terminal interface.  I end up with paginated junk:

t---ype <return> to continue, or q <return> to quit
GNU gdb 6.8
t---ype <return> to continue, or q <return> to quit
Copyright (C) 2008 Free Software Foundation, Inc.
t---ype <return> to continue, or q <return> to quit
t---nse GPLv3+: GNU GPL version 3 or later <http:/---Type <return> to continue, or q <return> to quit

I had to hit C/R in the terminal window to get each of these lines.
Sometimes it works better than others...

* The remote GDB doesn't seem to be well integrated with anjuta (not a criticism, just an observation) - none of the debug buttons on the main window are enabled, the whole interface seems to be in the terminal window, etc.  Is this expected, or did I miss something when building or installing?
Comment 2 liping Ke 2010-05-20 04:46:17 UTC
(In reply to comment #0)
> This is a pretty killer feature but is disabled by default (requiring a
> configure flag to enable it at build time).
> 
> We should make sure this is rock solid and enable by default.
> 

(In reply to comment #1)
> We'll need to thoroughly test and fix up issues such as those noted on the list
> by Gary:
> 
> * The local connection to GDB seems to have trouble with the anjuta terminal
> interface.  I end up with paginated junk:
> 
> t---ype <return> to continue, or q <return> to quit
> GNU gdb 6.8
> t---ype <return> to continue, or q <return> to quit
> Copyright (C) 2008 Free Software Foundation, Inc.
> t---ype <return> to continue, or q <return> to quit
> t---nse GPLv3+: GNU GPL version 3 or later <http:/---Type <return> to continue,
> or q <return> to quit
> 
> I had to hit C/R in the terminal window to get each of these lines.
> Sometimes it works better than others...
> 
> * The remote GDB doesn't seem to be well integrated with anjuta (not a
> criticism, just an observation) - none of the debug buttons on the main window
> are enabled, the whole interface seems to be in the terminal window, etc.  Is
> this expected, or did I miss something when building or installing?
> 
Hi, Josh

Do you know how to reproduce this phenomenon? I can't reproduce here. gdb local is executed in the vte terminal plugin, in Anjuta_IDE, it calls vte_terminal_fork_command to execute the gdb local command. So do you know the anjuta version as well as vte version he's using? If the terminal output is wrong, it is well possible be the problem of vte-plugin. (vte_terminal_fork_command) instead of poky plugin.

There's another bug 2060 related to local debug failure. I will focus on that bug since even if error is detected, error information printed, the terminal still hang there.
criping
Comment 3 Joshua Lock - Disabled 2010-05-20 11:20:03 UTC
(In reply to comment #2)
> Do do you know the
> anjuta version as well as vte version he's using? If the terminal output is
> wrong, it is well possible be the problem of vte-plugin.
> (vte_terminal_fork_command) instead of poky plugin.

Not sure, I've added Gary to the CC to see if he can help us debug this.

Gary, can you share your vte and anjuta versions per Criping's request?

Thanks!

Comment 4 liping Ke 2010-05-21 03:54:07 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > Do do you know the
> > anjuta version as well as vte version he's using? If the terminal output is
> > wrong, it is well possible be the problem of vte-plugin.
> > (vte_terminal_fork_command) instead of poky plugin.
> 
> Not sure, I've added Gary to the CC to see if he can help us debug this.
> 
> Gary, can you share your vte and anjuta versions per Criping's request?
> 
> Thanks!
> 

Hi, Josh
I did find vte_terminal_fork_command has many problem. I have fired a bug for anjuta vte terminal plugin. Please refer to https://bugzilla.gnome.org/show_bug.cgi?id=619253

This bug is similar with 2060, 2062. I will have some workaround update on 2060. and make 2062 the repeated bug as 2060.

Thanks& Regards,
criping
Comment 5 Joshua Lock - Disabled 2010-07-13 04:01:05 UTC
This was resolved in the 0.7.1 release
Comment 6 Joshua Lock - Disabled 2010-12-13 03:43:03 UTC
Verify this bug is fixed