Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2010-01

lazarus.lpi

4 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Juha Manninen

Hello!

How is one supposed to modify and debug Lazarus internals?

Earlier I understood that the project lazarus.lpi is not meant for debugging and hence its compiler options has "compile", "build" and "run" turned off.

When changing the Build Lazarus dialog I included that unit in lazarus.lpi, enabled the compiler options and debugged with it. I didn't find any other way to do it (and didn't want to use command line GDB). I even tried to make a test project that just opens that one dialog. I defined all needed paths to that project and it compiled but there were run time errors because some things were not initialized.

So, how do other people do it, if not using lazarus.lpi?

During debugging lazarus.lpi I noticed that Lazarus compiled for QT bindings hogs more memory than GTK2 bindings version. I don't know why, in normal usage I don't see any difference.
I have only 500 MB of main memory now. It is enough for anything else I do but debugging lazarus.lpi would need more. (I don't do Java development or such with this machine).

Juha Manninen

Reply by email

Paul Ishenin
to Juha Manninen
Juha Manninen wrote 5 lines
How is one supposed to modify and debug Lazarus internals? Earlier I understood that the project lazarus.lpi is not meant for debugging and hence its compiler options has "compile", "build" and "run" turned off.

Open lazarus.lpi and press F9 - this is what I do. It does not recompile anything (well, last month it recompiles codetools sometimes) - just launch another IDE in the debugger.

When changing the Build Lazarus dialog I included that unit in lazarus.lpi, enabled the compiler options and debugged with it. I didn't find any other way to do it (and didn't want to use command line GDB).

Yes. It would be nice to have attach to process debugger command available in the IDE but currently lazarus does not have it althout gdb supports this and debugs rather well.

So, how do other people do it, if not using lazarus.lpi?

Opening lazarus.lpi and press F9 :)

Best regards,
Paul Ishenin.

Reply by email

Juha Manninen
to Paul Ishenin
Paul Ishenin wrote 18 lines
Juha Manninen wrote: > How is one supposed to modify and debug Lazarus internals? > > Earlier I understood that the project lazarus.lpi is not meant for > debugging and hence its compiler options has "compile", "build" and "run" > turned off. Open lazarus.lpi and press F9 - this is what I do. It does not recompile anything (well, last month it recompiles codetools sometimes) - just launch another IDE in the debugger. > When changing the Build Lazarus dialog I included that unit in > lazarus.lpi, enabled the compiler options and debugged with it. I didn't > find any other way to do it (and didn't want to use command line GDB). Yes. It would be nice to have attach to process debugger command available in the IDE but currently lazarus does not have it althout gdb supports this and debugs rather well.

That works, good.
It also mostly solved my memory swapping problem. Less memory is used now and things are snappy again. Only minor problem is that the development is not so "RAD" any more when I need to compile from command line.

I noticed that sometimes when I try to inspect a variable by moving mouse over it, codetools start allocating lots of memory and do something intensively. It was a problem when my machine started swapping, now the delays are short. I guess this is a known issue.

Juha Manninen

Reply by email

Mattias Gaertner
to Juha Manninen
Show quoted text 29 lines
On tiistai, 5. tammikuuta 2010 15:52:13 Paul Ishenin wrote: > Juha Manninen wrote: > > How is one supposed to modify and debug Lazarus internals? > > > > Earlier I understood that the project lazarus.lpi is not meant for > > debugging and hence its compiler options has "compile", "build" and "run" > > turned off. > > Open lazarus.lpi and press F9 - this is what I do. It does not recompile > anything (well, last month it recompiles codetools sometimes) - just > launch another IDE in the debugger. > > > When changing the Build Lazarus dialog I included that unit in > > lazarus.lpi, enabled the compiler options and debugged with it. I didn't > > find any other way to do it (and didn't want to use command line GDB). > > Yes. It would be nice to have attach to process debugger command > available in the IDE but currently lazarus does not have it althout gdb > supports this and debugs rather well. That works, good. It also mostly solved my memory swapping problem. Less memory is used now and things are snappy again. Only minor problem is that the development is not so "RAD" any more when I need to compile from command line. I noticed that sometimes when I try to inspect a variable by moving mouse over it, codetools start allocating lots of memory and do something intensively. It was a problem when my machine started swapping, now the delays are short. I guess this is a known issue.

If you work in the lazarus sources, easily 50mb of sources are involved, parsed and trees are built. About 90mb ram is needed. But fragmentation can increase this to 200mb.

Mattias

Reply by email