KDevelop-1.1-beta1.0 Objective-C patch - using the Debugger with objc

[Richard Dale]

Thanks for adding the gdb path config option.

I don't think having an option to pass arguments to gdb is important - I was
only doing '-x /tmp/gdb.env' it to attempt to set up $LD_LIBRARY_PATH for the
app being debugged. So the most useful feature for me would be able to define
that environment variable under one of the tabs in 'Project->Options...' -
called 'Runtime Environment' or 'Runtime Options' perhaps.

On Fri, 21 Jan 2000, you wrote:
> Grab the latest sources from cvs and see what you think.
> BTW At the moment the "creating a new project" is broken so be careful.
> Hopefully soemone will fix this soon.
Yes, I may try that, but the next thing I need to do is to work on 'creating a
new Objective-C project' in KDevelop, and sorting out automake. So I really
need to have that bit of KDevelop working to patch against unfortunately...

-- Richard

On Fri, 21 Jan 2000, you wrote:
> On Thu, 20 Jan 2000, you wrote:
> 
> > > However, I like to keep my patched gdb in '/usr/local/bin' and the standard one
> > > in '/usr/bin' - so it would be useful to configure the path. 
> > 
> > Okay. I'll add an option into the config file. Is this worth adding to the
> > debug options dialog though? Perhaps... Hmmm
> 
> Added config option "GDB path"
> So in the config file do
> 
> [Debug]
> GDB path=/blah/de/blah/
> 
> The trailing slash is needed as I just concat this with "gdb" and default the
> path to "" in the normal case.
> 
> This is read everytime you start a gdb session.
> 
> > > I couldn't get the GNUstep test app 'Edit.app' to run when statically
> > > linked (using a 'make debug=yes shared=no' command). So, to run the dynamically
> > > linked version, I started KDevelop from the command line to pick up a suitable
> > > value of $LD_LIBRARY_PATH. Then everything worked. I tried adding a '-x
> > > /tmp/gdb/env' command under 'Set debug arguments', but I don't think it was
> > > being passed to gdb.
> > 
> > Ah, that's being passed to the application not to the gdb startup. Not a good
> > description. I'll change that to
> > "Set app arguments when debugging"
> > OR
> > I could use the "Execute with arguments" arguments and use this for gdb
> > arguments. The problem with this, is that you have to startup your app with
> > "Execute with arguments" first.
> > OR
> > I could do "Debug with argruments" so that it works like "Execute with
> > arguments" _and_ have gdb arguments as well?
> 
> Have done the "Debug with arguments" but I haven't done gdb arguments. I'm
> not sure I want to do the arguments to gdb as I see protential there for the
> user to really stuff things up. If this is really inconvient for you then I'll
> reconsider.
> 
> Grab the latest sources from cvs and see what you think.
> BTW At the moment the "creating a new project" is broken so be careful.
> Hopefully soemone will fix this soon.
> 
> -- 
> Regards,
> 
> jbb
> http://homepages.ihug.co.nz/~jbb
> ICQ: 60412209