[prev in list] [next in list] [prev in thread] [next in thread] 

List:       quanta
Subject:    Re: [Quanta] Directory Mapping dialog EVERY time I debug after
From:       Kimberly Lazarski <kim () biyn ! com>
Date:       2005-03-21 15:52:54
Message-ID: 1111420373.17705.10.camel () kim2p3lin ! biyn ! local
[Download RAW message or body]

On Sun, 2005-03-20 at 03:33, Linus McCabe wrote:
> On Sunday 20 March 2005 06.30, Kimberly Lazarski wrote:
> > When I try defining a breakpoint in
> > /srv/www/htdocs/Gubed/GubedTest/tests/variables/index.php it prompts me
> > for the basedirs,
> >
> > I tried changing the project basedirs to
> 
> It seems to me those basedirs should've worked. if the project is local on the 
> box, no basedirs should be necessary.

Really!  I thought they were always necessary per werner's  solution to
my 3.3.2 issues some weeks ago. The files were local then as well - not
on am SMB or NFS share, and I was running into different-but-related
issues.

> 
> I think I've found the reason thats the cause of your problem. You never said 
> if entering basedirs in the mapping dialog helped, only that you could use 
> cancel to skip it. Please try and enter them there and see if there's a 
> difference, because the dialog will remember previous entries and shouln't 
> pop up again if the previous entries work.

Even if I enter the basedirs in that dialog I still get prompted each
subsequent time I try to set a breakpoint, when I initiate a debug
session, and when Quanta switches to each individual file.

> 
> (Since your project is local, you can try with just a / as both basedirs)

Interesting - I will try that shortly and post back the results.

> 
> > incidentally, while debugging, does Quanta *have* to draw each file and
> > each line as it is debugging? This slows execution down terribly. On
> 
> No, it doesent. I constantly curse my self for my bad english and the poor 
> choice of words when i first made gubed. 

You're the Gubed author? I'm impressed - it's a great solution for a
difficult problem. As a user I'd like to thank you for that
contribution. :)

> 
> Currently:
> Run: Shows every command it executes
> Leap: Exeutes until a breakpoint or error (or pause) occurs. (what most people 
> think run does ;)

I thought that was what Leap was supposed to do but it does not seem to
stop on my breakpoints. :(

> 
> (What is now called 'run' will be renamed to 'trace', and whats now called 
> 'leap' will be renamed to 'run'. Most likely in next version)

I haven't looked at the Quanta source but isn't that just a resource and
worthy of a point-release or making it into one of the nightly builds? 

> 
> > it just draws the file in question and brings focus to that line of code
> > - execution while debugging is nearly as fast as release mode.
> 
> Try 'leap' and I think youll find it considerably faster than 'run'

I did but it doesn't seem to honor breakpoints at that point. :(

Thanks for your time, Linus!

--Kim

> 
> /LInus
> 
> > Thanks for the reply Linus.
> >
> > --Kim
-- 
No virus found in this email - I run Linux. ;)
_______________________________________________
Quanta mailing list
Quanta@mail.kde.org
https://mail.kde.org/mailman/listinfo/quanta
[prev in list] [next in list] [prev in thread] [next in thread]