Sign in Join

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

Mailing lists / lazarus / 1999-05

CVS Updated

19 messages · 5 people ·

Reply by email Subscribe to this list Your subscription

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

Shane Miller

I haven't been successful in reproducing the error in a minimal amount of code. One reason for this is that I still don't believe that that's the problem. Here's what I discovered.

If I take line 339 and copy it before line 337 (both are NOT commented out) then it will crash, but if I leave it the way it is (337 before 339) then it works fine.

Try it, Copy and move line 339 in front of 337 and open controls.pp. It'll crash.

If the line "Writeln('Buffer, Texts '+buffer[i]+'----'+texts+'-');" executes before (or without) line "Writeln('Length ='+Inttostr(Length(Buffer)));" then it crashes. If they both execute, but the second one (length ='+inttostr(Length(Buffer[i])))'); ) executes before the first it'll be fine. Wierd huh?

Hope I didn't confuse anyone.
Michael can you use this to solve the problem instead of me creating another source file with the problem? I'm not sure I'll be able to create it again. (not on purpose anyways) :-)

Shane

>> Michael Van Canneyt 05/25 8:51 AM >>>
Shane Miller wrote 30 lines
>>> Michael Van Canneyt 05/25 4:51 AM >>> On Mon, 24 May 1999, Michael A. Hess wrote: > Shane Miller wrote: > > > > 2) Run it, if you CAN open a file then go into the EDITOR.pp file and > > comment out line number 337 (a writeln) and run it again. Does it > > crash? Mine does. > > > > Can anyone figure out why commenting out a WRITELN would cause it to > > crawsh? > > It isn't the writeln that is causing the problem it is the IntToStr that > is causing the problem. Comment out the writeln and replace it with > something like > > temp := InttoStr(3); > > where temp was defined as an integer. > > You will see that it now also still works correctly. It looks like > something with strings is being fixed with the IntToStr call. >>Nope, temp ansistring management :( So what can be done about this?

Make MINIMAL code that reproduces this, and we'll fix it ASAP.

And by MINIMAL I understand a standalone program that can be compiled with the minimum of neede units. I.e. no FCL, GTK etc. (just trying to lure you out of 'compile lazarus, line .. in ..' :-) )

Florian has done a MAJOR overhaul of the ansistrings code, but apparently, not everything has been fixed yet :(

Michael.

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

Reply by email

Shane Miller

Did you update lazarus from CVS or the rntire FPC?

Shane

>> Payne Thomas E CNIN 05/26 10:10 AM >>>

Shane,

I updated from CVS this morning. I compiled and was able to open files. The files were colorized and the scanner spewed info to the text window. I even opened the files that the flat IDE had problems with lazaruside/idesourceutil.pp and lazaruside/lazaruside.pp, both at the same time.

I then tried #2 below... It still worked???

Tom

Show quoted text 32 lines
-----Original Message----- From: Shane Miller Sent: Monday, May 24, 1999 4:24 PM To: Subject: [lazarus] CVS Updated CVS is updated with the latest. Here's the issues..... 1). You have to change the declaration of gtk_shrink gtk_fill and gtk_expand to the 1.1 version of their declaration in gtkenums.pp in order for this to compile. 2) Run it, if you CAN open a file then go into the EDITOR.pp file and comment out line number 337 (a writeln) and run it again. Does it crash? Mine does. Can anyone figure out why commenting out a WRITELN would cause it to crawsh? Please we can figure this out then I can move ahead quickly..... BTW, I downloaded the latest snapshot today.... Thanks Shane _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus

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

Reply by email

Payne Thomas E CNIN

Shane,

I updated from CVS this morning. I compiled and was able to open files. The files were colorized and the scanner spewed info to the text window. I even opened the files that the flat IDE had problems with lazaruside/idesourceutil.pp and lazaruside/lazaruside.pp, both at the same time.

I then tried #2 below... It still worked???

Tom

Show quoted text 32 lines
-----Original Message----- From: Shane Miller Sent: Monday, May 24, 1999 4:24 PM To: Subject: [lazarus] CVS Updated CVS is updated with the latest. Here's the issues..... 1). You have to change the declaration of gtk_shrink gtk_fill and gtk_expand to the 1.1 version of their declaration in gtkenums.pp in order for this to compile. 2) Run it, if you CAN open a file then go into the EDITOR.pp file and comment out line number 337 (a writeln) and run it again. Does it crash? Mine does. Can anyone figure out why commenting out a WRITELN would cause it to crawsh? Please we can figure this out then I can move ahead quickly..... BTW, I downloaded the latest snapshot today.... Thanks Shane _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus

Reply by email

Baeseman, Cliff

I will try the switches maybe that is my problem.
Cliff

Earlier message 26 lines
-----Original Message----- From: Michael Van Canneyt Sent: Tuesday, May 25, 1999 10:23 AM To: Subject: RE: [lazarus] CVS Updated On Tue, 25 May 1999, Baeseman, Cliff wrote: > Has anyone tried this... > > Writeln('test' + inttoStr(2)) > > > This will alway throw error. Works fine here with today's sources. Both with $H+ and $H- Michael. _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus

Reply by email

Michael Van Canneyt
to Shane Miller: So what can be done about this? Shane
Shane Miller wrote 30 lines
>>> Michael Van Canneyt 05/25 4:51 AM >>> On Mon, 24 May 1999, Michael A. Hess wrote: > Shane Miller wrote: > > > > 2) Run it, if you CAN open a file then go into the EDITOR.pp file and > > comment out line number 337 (a writeln) and run it again. Does it > > crash? Mine does. > > > > Can anyone figure out why commenting out a WRITELN would cause it to > > crawsh? > > It isn't the writeln that is causing the problem it is the IntToStr that > is causing the problem. Comment out the writeln and replace it with > something like > > temp := InttoStr(3); > > where temp was defined as an integer. > > You will see that it now also still works correctly. It looks like > something with strings is being fixed with the IntToStr call. >>Nope, temp ansistring management :( So what can be done about this?

Make MINIMAL code that reproduces this, and we'll fix it ASAP.

And by MINIMAL I understand a standalone program that can be compiled with the minimum of neede units. I.e. no FCL, GTK etc. (just trying to lure you out of 'compile lazarus, line .. in ..' :-) )

Florian has done a MAJOR overhaul of the ansistrings code, but apparently, not everything has been fixed yet :(

Michael.

Reply by email

Michael Van Canneyt
to Michael A. Hess: It isn't the writeln that is causing the problem it is the IntToStr that is causing the…
Michael A. Hess wrote 19 lines
Shane Miller wrote: > > 2) Run it, if you CAN open a file then go into the EDITOR.pp file and > comment out line number 337 (a writeln) and run it again. Does it > crash? Mine does. > > Can anyone figure out why commenting out a WRITELN would cause it to > crawsh? It isn't the writeln that is causing the problem it is the IntToStr that is causing the problem. Comment out the writeln and replace it with something like temp := InttoStr(3); where temp was defined as an integer. You will see that it now also still works correctly. It looks like something with strings is being fixed with the IntToStr call.

Nope, temp ansistring management :(

Michael.

Reply by email

Michael Van Canneyt
to Shane Miller: CVS is updated with the latest. Here's the issues..... 1). You have to change the…
Shane Miller wrote 8 lines
CVS is updated with the latest. Here's the issues..... 1). You have to change the declaration of gtk_shrink gtk_fill and gtk_expand to the 1.1 version of their declaration in gtkenums.pp in order for this to compile. 2) Run it, if you CAN open a file then go into the EDITOR.pp file and comment out line number 337 (a writeln) and run it again. Does it crash? Mine does. Can anyone figure out why commenting out a WRITELN would cause it to crawsh?

This would typically be related to ansistring problems :(

Michael.

Reply by email

Shane Miller

Has ANYONE other than Payne tried this? Has it worked? Could someone else try this please? The instructions are found below....

Payne, did you update all of FPC or simply update Lazarus from CVS? If I comment out the line 337 I get the error yet. I pulled the snapshot of the compiler today.

Shane

>> Payne Thomas E CNIN 05/26 10:10 AM >>>

Shane,

I updated from CVS this morning. I compiled and was able to open files. The files were colorized and the scanner spewed info to the text window. I even opened the files that the flat IDE had problems with lazaruside/idesourceutil.pp and lazaruside/lazaruside.pp, both at the same time.

I then tried #2 below... It still worked???

Tom

Show quoted text 32 lines
-----Original Message----- From: Shane Miller Sent: Monday, May 24, 1999 4:24 PM To: Subject: [lazarus] CVS Updated CVS is updated with the latest. Here's the issues..... 1). You have to change the declaration of gtk_shrink gtk_fill and gtk_expand to the 1.1 version of their declaration in gtkenums.pp in order for this to compile. 2) Run it, if you CAN open a file then go into the EDITOR.pp file and comment out line number 337 (a writeln) and run it again. Does it crash? Mine does. Can anyone figure out why commenting out a WRITELN would cause it to crawsh? Please we can figure this out then I can move ahead quickly..... BTW, I downloaded the latest snapshot today.... Thanks Shane _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus

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

Reply by email

Shane Miller

That worked fine for me too, with yesterdays snapshot...

>> Michael Van Canneyt 05/25 10:21 AM >>>
Cliff wrote 6 lines
Has anyone tried this... Writeln('test' + inttoStr(2)) This will alway throw error.

Works fine here with today's sources. Both with $H+ and $H-

Michael.

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

Reply by email

Shane Miller
>> Michael Van Canneyt 05/25 4:51 AM >>>
Michael A. Hess wrote 21 lines
Shane Miller wrote: > > 2) Run it, if you CAN open a file then go into the EDITOR.pp file and > comment out line number 337 (a writeln) and run it again. Does it > crash? Mine does. > > Can anyone figure out why commenting out a WRITELN would cause it to > crawsh? It isn't the writeln that is causing the problem it is the IntToStr that is causing the problem. Comment out the writeln and replace it with something like temp := InttoStr(3); where temp was defined as an integer. You will see that it now also still works correctly. It looks like something with strings is being fixed with the IntToStr call. >Nope, temp ansistring management :(

So what can be done about this?

Shane

Reply by email

Michael A. Hess
to Shane Miller: CVS is updated with the latest. Here's the issues..... 1). You have to change the…
Shane Miller wrote 7 lines
2) Run it, if you CAN open a file then go into the EDITOR.pp file and comment out line number 337 (a writeln) and run it again. Does it crash? Mine does. Can anyone figure out why commenting out a WRITELN would cause it to crawsh?

It isn't the writeln that is causing the problem it is the IntToStr that is causing the problem. Comment out the writeln and replace it with something like

temp := InttoStr(3);

where temp was defined as an integer.

You will see that it now also still works correctly. It looks like something with strings is being fixed with the IntToStr call.

==== Programming my first best destiny! ==== Michael A. Hess Miracle Concepts, Inc. http://www.miraclec.com

Reply by email

Baeseman, Cliff

Has anyone tried this...

Writeln('test' + inttoStr(2))

This will alway throw error.

Cliff

Earlier message 58 lines
-----Original Message----- From: Michael Van Canneyt Sent: Tuesday, May 25, 1999 8:28 AM To: Subject: Re: [lazarus] CVS Updated On Tue, 25 May 1999, Shane Miller wrote: > > > >>> Michael Van Canneyt 05/25 4:51 AM >>> > > > On Mon, 24 May 1999, Michael A. Hess wrote: > > > Shane Miller wrote: > > > > > > 2) Run it, if you CAN open a file then go into the EDITOR.pp file and > > > comment out line number 337 (a writeln) and run it again. Does it > > > crash? Mine does. > > > > > > Can anyone figure out why commenting out a WRITELN would cause it to > > > crawsh? > > > > It isn't the writeln that is causing the problem it is the IntToStr that > > is causing the problem. Comment out the writeln and replace it with > > something like > > > > temp := InttoStr(3); > > > > where temp was defined as an integer. > > > > You will see that it now also still works correctly. It looks like > > something with strings is being fixed with the IntToStr call. > > >>Nope, temp ansistring management :( > > So what can be done about this? Make MINIMAL code that reproduces this, and we'll fix it ASAP. And by MINIMAL I understand a standalone program that can be compiled with the minimum of neede units. I.e. no FCL, GTK etc. (just trying to lure you out of 'compile lazarus, line .. in ..' :-) ) Florian has done a MAJOR overhaul of the ansistrings code, but apparently, not everything has been fixed yet :( Michael. _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus

Reply by email

Shane Miller

CVS is updated with the latest. Here's the issues.....

1). You have to change the declaration of gtk_shrink gtk_fill and gtk_expand to the 1.1 version of their declaration in gtkenums.pp in order for this to compile.

2) Run it, if you CAN open a file then go into the EDITOR.pp file and comment out line number 337 (a writeln) and run it again. Does it crash? Mine does.

Can anyone figure out why commenting out a WRITELN would cause it to crawsh?

Please we can figure this out then I can move ahead quickly.....

BTW, I downloaded the latest snapshot today....

Thanks
Shane

Reply by email

Baeseman, Cliff

when it rains it pours two gtk ide's

Cliff

Earlier message 55 lines
-----Original Message----- From: Payne Thomas E CNIN Sent: Wednesday, May 26, 1999 10:14 AM To: '' Subject: RE: [lazarus] CVS Updated Shane, I updated from CVS this morning. I compiled and was able to open files. The files were colorized and the scanner spewed info to the text window. I even opened the files that the flat IDE had problems with lazaruside/idesourceutil.pp and lazaruside/lazaruside.pp, both at the same time. I then tried #2 below... It still worked??? Tom > -----Original Message----- > From: Shane Miller > Sent: Monday, May 24, 1999 4:24 PM > To: > Subject: [lazarus] CVS Updated > > CVS is updated with the latest. Here's the issues..... > > 1). You have to change the declaration of gtk_shrink gtk_fill and > gtk_expand to the 1.1 version of their declaration in gtkenums.pp in order > for this to compile. > > 2) Run it, if you CAN open a file then go into the EDITOR.pp file and > comment out line > number 337 (a writeln) and run it again. Does it crash? Mine does. > > Can anyone figure out why commenting out a WRITELN would cause it to > crawsh? > > Please we can figure this out then I can move ahead > quickly..... > > BTW, I downloaded the latest snapshot today.... > > Thanks > Shane > > > _________________________________________________________________ > To unsubscribe: mail with > "unsubscribe" as the Subject > archives at http://www.miraclec.com/list_archives/lazarus _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus

Reply by email

Baeseman, Cliff

Shane I will try it for you when I get home and post the result to the list.

Just to let you know how it goes.

Cliff

Earlier message 74 lines
-----Original Message----- From: Shane Miller Sent: Wednesday, May 26, 1999 1:21 PM To: Subject: Re: RE: [lazarus] CVS Updated Has ANYONE other than Payne tried this? Has it worked? Could someone else try this please? The instructions are found below.... Payne, did you update all of FPC or simply update Lazarus from CVS? If I comment out the line 337 I get the error yet. I pulled the snapshot of the compiler today. Shane >>> Payne Thomas E CNIN 05/26 10:10 AM >>> Shane, I updated from CVS this morning. I compiled and was able to open files. The files were colorized and the scanner spewed info to the text window. I even opened the files that the flat IDE had problems with lazaruside/idesourceutil.pp and lazaruside/lazaruside.pp, both at the same time. I then tried #2 below... It still worked??? Tom > -----Original Message----- > From: Shane Miller > Sent: Monday, May 24, 1999 4:24 PM > To: > Subject: [lazarus] CVS Updated > > CVS is updated with the latest. Here's the issues..... > > 1). You have to change the declaration of gtk_shrink gtk_fill and > gtk_expand to the 1.1 version of their declaration in gtkenums.pp in order > for this to compile. > > 2) Run it, if you CAN open a file then go into the EDITOR.pp file and > comment out line > number 337 (a writeln) and run it again. Does it crash? Mine does. > > Can anyone figure out why commenting out a WRITELN would cause it to > crawsh? > > Please we can figure this out then I can move ahead > quickly..... > > BTW, I downloaded the latest snapshot today.... > > Thanks > Shane > > > _________________________________________________________________ > To unsubscribe: mail with > "unsubscribe" as the Subject > archives at http://www.miraclec.com/list_archives/lazarus _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus

Reply by email

Baeseman, Cliff

What procedure is it blowing in? Is it the save to file routine.

I had something like that occuring last night but fixed it somehow by manipulating the
way I was doing it.

Cliff

Earlier message 30 lines
-----Original Message----- From: Michael A. Hess Sent: Wednesday, May 26, 1999 1:56 PM To: Subject: Re: [lazarus] CVS Updated Shane Miller wrote: > > Has ANYONE other than Payne tried this? Has it worked? Could someone > else try this please? The instructions are found below.... > > Payne, did you update all of FPC or simply update Lazarus from CVS? > If I comment out the line 337 I get the error yet. I pulled the > snapshot of the compiler today. I just did an update out of CVS, 2:30PM EST. Rebuilt the compiler, FCL, GTK, AND lazarus. It still blowsup if line 337 is commented out. With the line in it works. :-\ -- ==== Programming my first best destiny! ==== Michael A. Hess Miracle Concepts, Inc. http://www.miraclec.com _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus

Reply by email

Michael A. Hess
to Shane Miller: Has ANYONE other than Payne tried this? Has it worked? Could someone else try this…
Shane Miller wrote 7 lines
Has ANYONE other than Payne tried this? Has it worked? Could someone else try this please? The instructions are found below.... Payne, did you update all of FPC or simply update Lazarus from CVS? If I comment out the line 337 I get the error yet. I pulled the snapshot of the compiler today.

I just did an update out of CVS, 2:30PM EST. Rebuilt the compiler, FCL, GTK, AND lazarus. It still blowsup if line 337 is commented out. With the line in it works. :-\

==== Programming my first best destiny! ==== Michael A. Hess Miracle Concepts, Inc. http://www.miraclec.com

Reply by email

Payne Thomas E CNIN

Shane,
I updated all of FPC and lazarus around 0900 CST 5/26/99. CVS had an issue with stdcontrols.pp (I must have changed it or something). I blew it away and updated again. I did use my previously built version of 0.99.11 to compile the new 0.99.11. I am still using the ppc386.cfg you gave me.)

If you can deal with a ~3.5mb tgz, I will sent my version of FPC/Lazarus sources to you directly.

Tom

Show quoted text 29 lines
-----Original Message----- From: Michael A. Hess Sent: Wednesday, May 26, 1999 1:56 PM To: Subject: Re: [lazarus] CVS Updated Shane Miller wrote: > > Has ANYONE other than Payne tried this? Has it worked? Could someone > else try this please? The instructions are found below.... > > Payne, did you update all of FPC or simply update Lazarus from CVS? > If I comment out the line 337 I get the error yet. I pulled the > snapshot of the compiler today. I just did an update out of CVS, 2:30PM EST. Rebuilt the compiler, FCL, GTK, AND lazarus. It still blowsup if line 337 is commented out. With the line in it works. :-\ -- ==== Programming my first best destiny! ==== Michael A. Hess Miracle Concepts, Inc. http://www.miraclec.com _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus

Reply by email