yade-users team mailing list archive

[Bruno Chareyre <bruno.chareyre@xxxxxxxxxxx>]

You'll have to show me what you do Jerome. Did you try on virgin trunk? 
I'm wondering if you didn't mix kdev files from bzr with your older 
project files.

For debugging, it seems kdevelop can catch breakpoints only if the 
attached process is Qt interface. If Qt is not open, it seems the 
process will never be stopped. I'm still experimenting.
The straightforward debbuging where kdevelop start the process itself 
doesn't work as kdevelop doens't recognize python script as debugable 
executable.

Bruno



On 18/06/10 16:27, Jerome Duriez wrote:
> Hello,
>
>     In fact if you can not launch kdevelop (which is let us say a 
> program code editor), I'm afraid it is not a Yade problem, but a Linux 
> one. It will depend especially of your linux distribution.
>
> Jerome
>
> Le 18/06/2010 08:30, yyu a écrit :
> > Hello everyone,
> >
> >     Is there some difference among yade-0.50 and former versions 
> > (such as
> > yade-0.20) on debugging codes? I tried two methods according to the
> > websit ( https://yade-dem.org/wiki/Debugging_using_Kdevelop), but lost
> > to open kdevelop. Finally, when running sudo apt-get install kdevelop in
> > terminal, my computer tells me as the following:
> >
> > Reading package lists...Done
> > Building dependency tree
> > Reading state information ...Done
> > Package kdevelop is not available, but is referred to by another
> > package.
> > This may mean that the package is missing, has been obsoleted, or is
> > only availabe from another source
> > However the following packages replace it:
> >   kdevplatform1-libs
> > E: Package kdevelop has no installation candiate
> >
> > How can I use debugging on yade-0.50?Thanks a lot
> >
> > Regard,
> > yaowei yu