[Lazarus] highlight colours per file.

2014-07-21 Thread Marco van de Voort

I working on a header generation tool for some C project.

For that I open .ini and .h files, and I notice that they are highlighted
differently (classic layout).   .h is blue on blue and hard to read, while
ini is yellow on black.

Where can adjust how files are highlighted by extension (lazarus trunk)

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus


Re: [Lazarus] CodeCompletion: Unit not found, compile ok

2014-07-21 Thread Marco van de Voort
On Sun, Jul 20, 2014 at 06:40:30PM +, Lukas Gradl wrote:
> > In our previous episode, Lukas Gradl said:
> >> I've a strange problem with Lazarus (1.3, SVN 45936M):
> >
> > Is my guess correct that you also use a trunk version of FPC?
> 
> Yes, your guess is correct. I use the latest fpc-svn as well.

There variants moved out of the RTL to packages. When I read how you
resolved it, probably the old cached index still had it in the RTL dir.

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus


Re: [Lazarus] Need testers for the a new debugger

2014-07-21 Thread Joost van der Sluis
> 2014.07.14. 23:13 keltezéssel, Joost van der Sluis írta:
> > To install the debugger just install the
> > components/lazdebuggers/lazdebuggerfp.lpk package.
> 
> Can anybody install on Win32?

I 've tried that myself again and it installed without any problems.

Maybe you can try to run the Lazarus itself in GDB, after you've installed the 
package. Then when you get the 'out of memory' problem, type 'bt' and send us 
the backtrace.

If you do not know how to work with GDB from the console, look here: 
http://wiki.freepascal.org/Creating_a_Backtrace_with_GDB

Joost.--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus


Re: [Lazarus] highlight colours per file.

2014-07-21 Thread Mattias Gaertner
On Mon, 21 Jul 2014 11:31:01 +0200
Marco van de Voort  wrote:

> 
> I working on a header generation tool for some C project.
> 
> For that I open .ini and .h files, and I notice that they are highlighted
> differently (classic layout).   .h is blue on blue and hard to read, while
> ini is yellow on black.
> 
> Where can adjust how files are highlighted by extension (lazarus trunk)

Editor / Display / Colors, at the top is the list of file extensions.

Mattias

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus


Re: [Lazarus] CodeCompletion: Unit not found, compile ok

2014-07-21 Thread Mattias Gaertner
On Mon, 21 Jul 2014 11:32:23 +0200
Marco van de Voort  wrote:

> On Sun, Jul 20, 2014 at 06:40:30PM +, Lukas Gradl wrote:
> > > In our previous episode, Lukas Gradl said:
> > >> I've a strange problem with Lazarus (1.3, SVN 45936M):
> > >
> > > Is my guess correct that you also use a trunk version of FPC?
> > 
> > Yes, your guess is correct. I use the latest fpc-svn as well.
> 
> There variants moved out of the RTL to packages. When I read how you
> resolved it, probably the old cached index still had it in the RTL dir.

Yes.

Maybe it is possible to detect a svn update in the fpc sources and do
the rescan automatically.

Mattias

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus


Re: [Lazarus] highlight colours per file.

2014-07-21 Thread Marco van de Voort
On Mon, Jul 21, 2014 at 11:44:05AM +0200, Mattias Gaertner wrote:
> > Where can adjust how files are highlighted by extension (lazarus trunk)
> 
> Editor / Display / Colors, at the top is the list of file extensions.

Thanks. I missed that topline. For now I moved "h" from C++ to INI, and that
does what I hoped for.

Small question left, if I didn't select anything it reverted to some weird
style. What is the style for extensions not named otherwise?

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus


Re: [Lazarus] Need testers for the a new debugger

2014-07-21 Thread Gabor Boros

2014.07.21. 11:42 keltezéssel, Joost van der Sluis írta:


I 've tried that myself again and it installed without any problems.

Maybe you can try to run the Lazarus itself in GDB, after you've
installed the package. Then when you get the 'out of memory' problem,
type 'bt' and send us the backtrace.

If you do not know how to work with GDB from the console, look here:
http://wiki.freepascal.org/Creating_a_Backtrace_with_GDB

Joost.


Tried with 45950 (FPC 2.6.4) and got the attached error.

Gabor
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus


Re: [Lazarus] Need testers for the a new debugger

2014-07-21 Thread Joost van der Sluis
> On 20/07/14 15:47, Joost van der Sluis wrote:
> I haven't seen the spurious SIGSEGV for a while, so maybe that is fixed. 
> I am still seeing the spurious leaving of a routine on pressing step 
> into on one particular begin, but mostly it looks good - I think it is 
> rather faster than the gdb debugger.

It's not that strange it's faster then the gdb-debugger, as gdb is an external 
application from which the output is parsed.

The step-into-next-line code is quite complicated. Just single-stepping until 
another procedure with line-info has been hit is too slow. So it uses 
watchpoints on the stack, so that the debuggee stops when a new procedure is 
being called, or the current procedure has ended. Then it compares the 
line-info with the line-info at the start of the step-into-next-line. It is 
very well possible that for some reason the start of the procedure is ignored, 
so that it immediately steps to the end of the procedure.

Can you create a small test-application with a procedure that has this problem? 
With some steps to reproduce?

If you want to look at it yourself, look at the TDbgControllerStepIntoLineCmd 
class in fpdbgcontroller.pas. The DoContinue function is called when the 
debuggee has to start running again.  When the debuggee stops running, 
ResolveEvent is being called. ResolveEvent has to set Finished to true if the 
command has finished. If Finished is set to false, DoContinue is called again, 
and the debuggee continues running.

> Not sure about the spurious step - I notice on some routines stepping 
> steps to the end line sometimes and then back into the routine. Perahps 
> it is related to this?

Do you have an example? It could be that the execution point really jumps 
up-and-down, or that the debug-info gives some strange results. 

Joost.--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus


Re: [Lazarus] Need testers for the a new debugger

2014-07-21 Thread Sven Barth
Am 21.07.2014 13:45 schrieb "Joost van der Sluis" :
> > Not sure about the spurious step - I notice on some routines stepping
> > steps to the end line sometimes and then back into the routine. Perahps
> > it is related to this?
>
> Do you have an example? It could be that the execution point really jumps
up-and-down, or that the debug-info gives some strange results.

This happens with GDB as well. Mostly in constructors. Or it's related to
implicit exception frames... :/

Regards,
Sven
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus


Re: [Lazarus] Need testers for the a new debugger

2014-07-21 Thread C Western

On 21/07/14 12:44, Joost van der Sluis wrote:

 > On 20/07/14 15:47, Joost van der Sluis wrote:
 > I haven't seen the spurious SIGSEGV for a while, so maybe that is fixed.
 > I am still seeing the spurious leaving of a routine on pressing step
 > into on one particular begin, but mostly it looks good - I think it is
 > rather faster than the gdb debugger.

It's not that strange it's faster then the gdb-debugger, as gdb is an
external application from which the output is parsed.

The step-into-next-line code is quite complicated. Just single-stepping
until another procedure with line-info has been hit is too slow. So it
uses watchpoints on the stack, so that the debuggee stops when a new
procedure is being called, or the current procedure has ended. Then it
compares the line-info with the line-info at the start of the
step-into-next-line. It is very well possible that for some reason the
start of the procedure is ignored, so that it immediately steps to the
end of the procedure.

Can you create a small test-application with a procedure that has this
problem? With some steps to reproduce?



Managed to create a small test program:

program tproj;

uses sysutils;

procedure a(const s: string);
var
  a: string;
  r: array [0..10] of Double;
begin
  a := s+s+s;
  r[8] := StrToFloat(a);
  WriteLn(a, ' ', r[8])
end;

begin
  a('6'); <<-Set break point here, and hit step into here twice
end.

First step into ends on begin in procedure, second on final end.
Seems to be related to size of stack frame - if I didn't have the array 
in, it works as expected. I compiled it with all stack checks on.


I know this stuff can be difficult - I have certainly seen some odd 
things with Delphi and gdb. My hope is we can resolve some of these 
things as we now have control over all parts of the system.


Colin


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus


[Lazarus] Laz trunk+FPC trunk Windows - experiences with help

2014-07-21 Thread Reinier Olislagers
Hi list,

I'm getting a lot of errors trying to get context-sensitive help with lhelp.
(in my patched copy of Lazarus; see second patch in
http://bugs.freepascal.org/view.php?id=24743)
Lhelp will start up but give "Cannot handle this type of subcontent:
"file://" for url: file://
It looks like the actual file name of the chm file is not being received
by lhelp.

Normally I would always blame the compiler and/or RTL/FCL for my own or
other people's incorrect code ;) but I'm starting to suspect recent
fixes in simpleipc may have messed things up.

I'm going to have a look at that but first wanted to know whether other
people with the config listed in the subject have the same issues (or
whether it's PEBKAC/machine dependent).

Alternatively, review and correction of the patch in
http://bugs.freepascal.org/view.php?id=24743
would be very welcome, too ;)

Finally, I would be grateful if somebody could indicate if my patch
works for FPC trunk+Lazarus trunk?

Thanks,
Reinier

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus