SVN support in kdevelop 3.4

[Andreas Pakulat]

On 29.10.05 20:30:51, Hamish Rodda wrote:
> On Saturday 29 October 2005 01:40, Andreas Pakulat wrote:
> > On 28.10.05 16:45:00, Andreas Pakulat wrote:
> > > On 28.10.05 16:01:42, Mickael Marchand wrote:
> > > > if the ioslave crashes, the thing I need is a backtrace of it which can
> > > > be obtained by reading kdebase/kioslave/DEBUG.howto :)
> > > > make sure to also enable the kio_svn debug area (kdebugdialog).
> > >
> > > Ok, I'll try that, I hope that doesn't involve building kdebase myself,
> > > because that is not quite comfortable...
> >
> > Ok, kdebugdialog doesn't seem to know kio_svn, thus I needed to activate
> > all kio* and from the source of 3.4.2 it looks like kio_svn uses
> > kdDebug() without a number... And I don't see any messages from the
> > kdebase kio_slave... I'll fetch the source for my kdebase later today.
> >
> > kioslave: ####### CRASH ###### protocol = kio_svn pid = 13103 signal = 11
> >
> > is all I can find
> >
> > Debugging is not exactly easy because after some seconds the slave
> > crashes even when it's suspended...
> >
> > Lets see... no, gdb doesn't start fast enough to be able to get a
> > meaningfull backtrace, the slave dies before... The output of "bt"
> > doesn't tell anything of value...
> 
> Have a look at kdebase/kioslave/DEBUG.howto

And then? There is not sentence explaining what to do if the slave dies
while I'm trying to attach gdb to it. I did all as explained in
DEBUG.howto and from the console output kdeinit suspends the slave
process, still it crashes a few seconds later and gdb doesn't come up
quick enough.

Any suggestions? BTW: the kio_svn slave works in konqueror...

Andreas

-- 
You will never know hunger.