GDB Problems

[Michael.Schmidt at L-3com.com]

Thanks, Alvin.  That was exactly the problem.  He can debug now, but he
gets a strange error dialog when he starts debugging.

"The debugger component encountered an internal error while processing a
reply from gdb. Please submit a bug report.

Details:
The exception is: MI type error
The MI response is: ^done"

Have you seen that before?

Thanks for you help.

> -----Original Message-----
> From: kdevelop-bounces at barney.cs.uni-potsdam.de [mailto:kdevelop-
> bounces at barney.cs.uni-potsdam.de] On Behalf Of Alvin Beach
> Sent: Wednesday, March 11, 2009 11:45 AM
> To: kdevelop at barney.cs.uni-potsdam.de
> Subject: Re: GDB Problems
> 
> On March 11, 2009 01:36:59 pm Michael.Schmidt at l-3com.com wrote:
> > Hello,
> >
> >
> >
> > I've been successfully using GDB in kdevelop, but a co-worker of
mine
> > has been having issues running GDB.  When he tries to start
debugging,
> > he gets a "Process Exited" message in the GDB window and the program
> > doesn't run.  He seems to have a newer version of GDB than I do.
> >
> >
> >
> > Please let me know what I should try to resolve the problem.  I'll
> > provide more information if it is needed.
> >
> >
> >
> > Thanks,
> >
> > Mike
> 
> I had this problem when I upgraded from openSUSE 10.3 to openSUSE
11.1.
> 
> What worked for me was adding '--mode=execute' in the project settings
> under
> Debugger.
> 
> 1. Project->Project Options
> 2. Debugger
> 3. In "Debugging shell:" it probably just says "libtool". If so mode
> switch:
>    libtool --mode=execute
> 
> That's should fix it.
> 
> Another thing to try is to make the "Debugging shell:" field empty.
I've
> seen
> that work. I typically just add the --mode switch.
> 
> The above applies to KDevelop 3 and an Automake Managed project.
> 
> Alvin
> 
> 
> _______________________________________________
> kdevelop mailing list
> kdevelop at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop