debugging kdevelop.bin doesn't work

[Milian Wolff]

On Monday 01 March 2010 01:12:08 Victor Vicente de Carvalho wrote:
> 2010/2/25 Niko Sams <niko.sams at gmail.com>:
> > On Thu, Feb 25, 2010 at 20:57, Andreas Pakulat <apaku at gmx.de> wrote:
> >> @#%#$$@!$@#$~!!!@@!! I had follow-fork-mode set to child in my .gdbinit
> >> 
> >> :) Which made gdb follow the first qmake call and when that one exited
> >> 
> >> gdb exited too... Thanks for hitting me with a brick wall into the right
> >> direction.
> >> 
> > :D
> > 
> > Glad you found the issue.
> > 
> > Niko
> > 
> > --
> > KDevelop-devel mailing list
> > KDevelop-devel at kdevelop.org
> > https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
> 
> It is possible to debug a plugin this way? From inside KDevelop?? I'd
> like to debug the php plugin

While this will work,  the much preferred way is to write a Unit Test and 
debug any issue there. What Problem do you want to investigate?


-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100301/362c4a79/attachment.sig>