Hello,
My plugins (https://github.com/ik5/split_lazarus) does almost all I want it to do, but not the way I want it to be made. What are the best ways to debug my code inside Lazarus ?
Thanks,
Ido
Mailing lists / lazarus / 2013-01
debugging a lazarus plugins
6 messages · 2 people ·
- ik 3
- Martin 3
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
ik wrote 6 lines
Hello,
My plugins (https://github.com/ik5/split_lazarus) does almost all I
want it to do, but not the way I want it to be made.
What are the best ways to debug my code inside Lazarus ?
Either debug the entire IDE (open ide/lazarus.lpi and hit F9), or write a test case.
Martin wrote 9 lines
On 28/01/2013 18:53, ik wrote:
> Hello,
>
> My plugins (https://github.com/ik5/split_lazarus) does almost all I
> want it to do, but not the way I want it to be made.
> What are the best ways to debug my code inside Lazarus ?
>
Either debug the entire IDE (open ide/lazarus.lpi and hit F9),
In which case, it may be helpful to use a 2nd primar-config-path, for diff window locations (or colors)... (I personally do not, I move them each time)
or write a test case.
Martin wrote 16 lines
On 28/01/2013 19:04, Martin wrote:
>
> On 28/01/2013 18:53, ik wrote:
>>
>> Hello,
>>
>> My plugins (https://github.com/ik5/split_lazarus) does almost all I
>> want it to do, but not the way I want it to be made.
>> What are the best ways to debug my code inside Lazarus ?
>>
>
> Either debug the entire IDE (open ide/lazarus.lpi and hit F9),
In which case, it may be helpful to use a 2nd primar-config-path, for diff
window locations (or colors)... (I personally do not, I move them each time)
I'm not sure that I understand you
Show quoted text 5 lines
> or write a test case.
How can I write a test case for such thing ?
I mean, it uses internal IDE stuff ...
Show quoted text 8 lines
--
_______________________________________________
Lazarus mailing list
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
ik wrote 14 lines
On Mon, Jan 28, 2013 at 9:06 PM, Martin wrote:
> On 28/01/2013 19:04, Martin wrote:
>> On 28/01/2013 18:53, ik wrote:
>>> Hello,
>>>
>>> My plugins (https://github.com/ik5/split_lazarus) does almost all I
>>> want it to do, but not the way I want it to be made.
>>> What are the best ways to debug my code inside Lazarus ?
>>>
>> Either debug the entire IDE (open ide/lazarus.lpi and hit F9),
>
> In which case, it may be helpful to use a 2nd primar-config-path, for diff
> window locations (or colors)... (I personally do not, I move them each time)
I'm not sure that I understand you
Well I just run the IDE in the debugger. That happens if I open ide/lazarus.lpi and hit F9
But it has the danger of mixing up debuggee and debugger
So if you use -pcp= in "run params" then you can save different window locations, or diff editor colrs, even diff config, and even load a diff lazarus.exe (as long as it is in sync with the ource you have open)
As I said, I do not use -pcp, I just move the window, after the debuggee . I have 2 screens so enough space
>> or write a test case. How can I write a test case for such thing ? I mean, it uses internal IDE stuff ...
The debugger has the same issue.
That is where I use the ide.lpk
You MUST rebuild the IDE from the tools menu, and then compile the test, if the test uses this package.
You get real nasty errors, if you compile the test, and it tries to compile the package !!!! Real nasty. ppu in wrong location. Only fix, by find and delete ppu
Martin wrote 36 lines
On 28/01/2013 19:15, ik wrote:
>
> On Mon, Jan 28, 2013 at 9:06 PM, Martin wrote:
>>
>> On 28/01/2013 19:04, Martin wrote:
>>>
>>> On 28/01/2013 18:53, ik wrote:
>>>>
>>>> Hello,
>>>>
>>>> My plugins (https://github.com/ik5/split_lazarus) does almost all I
>>>> want it to do, but not the way I want it to be made.
>>>> What are the best ways to debug my code inside Lazarus ?
>>>>
>>> Either debug the entire IDE (open ide/lazarus.lpi and hit F9),
>>
>>
>> In which case, it may be helpful to use a 2nd primar-config-path, for
>> diff
>> window locations (or colors)... (I personally do not, I move them each
>> time)
>
> I'm not sure that I understand you
Well I just run the IDE in the debugger. That happens if I open
ide/lazarus.lpi and hit F9
But it has the danger of mixing up debuggee and debugger
So if you use -pcp= in "run params" then you can save different window
locations, or diff editor colrs, even diff config, and even load a diff
lazarus.exe (as long as it is in sync with the ource you have open)
As I said, I do not use -pcp, I just move the window, after the debuggee . I
have 2 screens so enough space
Ended up using Debugln, and still can't figure out the problems I'm having (a new question to the mailing list)
Show quoted text 24 lines
>>> or write a test case.
>
> How can I write a test case for such thing ?
> I mean, it uses internal IDE stuff ...
>
The debugger has the same issue.
That is where I use the ide.lpk
You MUST rebuild the IDE from the tools menu, and then compile the test, if
the test uses this package.
You get real nasty errors, if you compile the test, and it tries to compile
the package !!!! Real nasty. ppu in wrong location. Only fix, by find and
delete ppu
--
_______________________________________________
Lazarus mailing list
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus