Help!

I have got still some problems with the current lcl. I have downloaded a new developer fpc and a new lazarus. Compiling the lcl is successful. But this results in broken dependency checksums. There are always some units left which depend on newer files. Recompiling the lcl four times allows compiling lazarus. But then starting lazarus:

LM_SCREENINIT called --> should go to GTKObject.Init TODO: check this
An unhandled exception occurred at 0x08052C9C :
Access violation
0x08052C9C
0x00000000

Starting other lcl programs seems to work. But as soon as moving the mouse they crash also.

Mattias

Hmm...wonder how delphi this does, since at work I never encountered this problem (there I use New).
There is a difference between the usage of Getmem and New. New initializes the record as well so in our case I would prefer the use new (and dispose) to Getmem. If rever the record changes you wouldn have to change the code elswere.

Marc

Hi

I have the same problem, too.
I use the newest fpc 1.1 and Lazarus from CVS and I get since some days this error:

laser:/mnt/lazarus # ./lazarus
LM_SCREENINIT called --> should go to GTKObject.Init TODO: check this
An unhandled exception occurred at 0x08052558 :
Access violation
0x08052558
0x00000000

Because of the not running Makefile I have compiled the source of Lazarus with to have some better debugging Infos (-glc)

ppc386 -B -glc -Fulcl -Filcl/include -Fulcl/interfaces/gtk -Fiinclude/linux -Fucomponents/mwedit -Fudesigner lazarus.pp

Now I have looked in DDD where this error is and it looks like that it is the line
NewPLResource^.Value:=Value;
in the file lresources.pp in procedure
TLResourceList.Add(Name,ValueType,Value:AnsiString);

cu Jens

>>>>>>>>>>>>>>>>> Urspr�ngliche Nachricht <<<<<<<<<<<<<<<<<<

Am 1/13/01, 2:14:47 PM, schrieb Mattias Gaertner
zum Thema Re: [lazarus] CVS Committed
01/12/2001:

mouse

they crash also.

Mattias

_________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus

But it's compiled with
{$H+}

Doesn't that cause it to use all ansistrings?

Shane

Changes:

TShiftState is calculated correctly now so on Key messages you can check if ssCtrl or ssShift are in the TShiftstate sent to the procedure.

Ctrl-Shift-Up and Down work in the editor IF your cursor is on the method name. If you are on the method name in the declaration, the cursor moves to the procedure in the implementation section. If you are in the implementation on a method and you press Shift-Ctrl-Up you'll go to the declaration of the method.

OpenFileAtCursor works better now. What you need to do is go into the Compiler Optinos and fill in the Other Units edit box. You fill in search paths seperated by semi-colons. For example:

/usr/local/fpc;/usr/local/lazarus;/usr/local/lazarus/lcl PROBLEM: When you select PROJECT - BUILD after doing this, the command line appears to get truncated after a certain length that the search directories cause it to surpass. This prevents Lazarus from compiling correctly. Ideas?

Another problem: I moved the {$I viewunits1.lrs} and viewforms1 and dlgmessage.lrs includes to their units so they aren't in main.pp. This worked fine except for dlgmessage.pp. When I did this, it would crash whenever the resource "default" was loaded for an image on the toolbar. I have no idea how these two things are related. I played with it, but haven't figured it out.

That's all for now.
Shane

You cant build lazarus correctly without makefile. of you want to add compiler options run make OPT=-glc

BTW if you want to hve a debug build, use make OPT=-dDEBUG

ppc386 -B -glc -Fulcl -Filcl/include -Fulcl/interfaces/gtk -Fiinclude/linux -Fucomponents/mwedit -Fudesigner lazarus.pp

Marc

At the risk of stating the obvious:

ShortString instead of ansistring ?

Michael.

Hi

If I try to compile the 1.0.5 Fixes-Compiler with the 1.0.4 I get many many of errors like these:

/tmp/fpc/compiler/ppc1 -Xs -OG2p3 -n -Fi../inc -Fi../i386 -Fi../unix -FE. -di386 -Us -Sg syslinux.pp
./syslinux.s: Assembler messages:
./syslinux.s:21: Error: suffix or operands invalid for `cmp' ./syslinux.s:25: Error: suffix or operands invalid for `and' ./syslinux.s:30: Error: suffix or operands invalid for `and' ./syslinux.s:31: Error: suffix or operands invalid for `shr' ./syslinux.s:46: Error: suffix or operands invalid for `cmp'

and so on and so on...

If I try it with the 1.1-Compiler it don't work, too.

Which compiler do I need or is there a ready to download rpm of 1.0.5 on the Lazarus-Homepage?

cu Jens

>>>>>>>>>>>>>>>>> Urspr�ngliche Nachricht <<<<<<<<<<<<<<<<<<

Am 1/13/01, 7:21:11 PM, schrieb "Michael A. Hess"
zum Thema [lazarus] Must Use 1.0.5 (was: CVS Committed 01/12/2001):

the

FIXBRANCH. I incountered this same thing until I used 1.0.5.

Jens wrote

I have the same problem, too. I use the newest fpc 1.1 and Lazarus from CVS and I get since some days this error:

It appears that it will not work with 1.1. You MUST use 1.0.5 from the FIXBRANCH. I incountered this same thing until I used 1.0.5.

cvs co -r FIXES_1_0_0 compiler
cvs co -r FIXES_1_0_0 rtl

This will build a 1.0.5 release of FPC. This seems to compile Lazarus fine and will not give the Violation.

Shane Miller wrote

But it's compiled with {$H+} Doesn't that cause it to use all ansistrings?

Even ShortStrings must be initialized with nil, because strings are pointers.
In objects this is done in InitInstance with
fillchar(instance^,self.instancesize,0);
For GetMem we must do it by ourselves.

Mattias

Jens wrote

Which compiler do I need or is there a ready to download rpm of 1.0.5 on the Lazarus-Homepage?

In a few minutes there will be. I'll keep the list informed

Marc

You are right.

The lresources.pp has a bug.
The AnsiStrings must be initialized with nil. Here is a better solution:

procedure TLResourceList.Add(Name,ValueType,Value:AnsiString);
var NewPLResource:PLResource;
begin
  GetMem(NewPLResource,SizeOf(LResource));
  Pointer(NewPLResource^.Name):=nil;
  Pointer(NewPLResource^.ValueType):=nil;
  Pointer(NewPLResource^.Value):=nil;
  NewPLResource^.Name:=Name;
  NewPLResource^.ValueType:=uppercase(ValueType);
  NewPLResource^.Value:=Value;
  FList.Add(NewPLResource);
end;

But this is not the only bug.
In tmessagedlg.lfm is Borderstyle used. As I have written earlier on this list, TBorderStyle is not streamable due to a bug in the fpc 1.1. Remove the Borderstyle line and rebuild the dlgmessage.lrs with the lazres program.

There is also the MouseMove bug. As soon as I move the mouse any LCL program crashes.