Sign in Join

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

Mailing lists / fpc-devel / 2007-03

MSEide+MSEgui and FPC 2.2

3 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

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

Martin Schreiber

Hi,
MSEide+MSEgui compiles and runs on Linux with FPC 2.1.1. It compiles on win32 but does not run.
Mantis 8481 ("By copying an record with OLE string fields, the memory location of the *source* string is changed.") is a show stopper for MSEgui, I can not do more debugging until the problem is solved.
Note that MSEgui runs on win32 if compiled with Delphi (Delphi has non reference counted widestrings too).
As you know, MSEgui is completely done with widestrings, it would be very valuable for MSEgui to have an reference counted widestring type on all platforms.
Another thing is Mantis 6690 ("RTTI is sometimes wrong for inherited interfaces.") and Mantis 6036 ("tobject.GetInterface should work with corba style interfaces.").
I could remove the ugly "{$ifdef FPC}{$INTERFACES CORBA}{$endif}" in every unit if the issues where solved.

Martin

Reply by email

Florian Klaempfl
to Martin Schreiber
Show quoted text 6 lines
Hi, MSEide+MSEgui compiles and runs on Linux with FPC 2.1.1. It compiles on win32 but does not run. Mantis 8481 ("By copying an record with OLE string fields, the memory location of the *source* string is changed.") is a show stopper for MSEgui, I can not do more debugging until the problem is solved.

Other ways are currently not doable with the current FPC widestring architecture. When does this cause problems? Making assumtions according to memory locations for managed strings is bad anyways?

Reply by email

Martin Schreiber
to Florian Klaempfl
Florian Klaempfl wrote 11 lines
Martin Schreiber schrieb: > Hi, > MSEide+MSEgui compiles and runs on Linux with FPC 2.1.1. > It compiles on win32 but does not run. > Mantis 8481 ("By copying an record with OLE string fields, the memory > location of the *source* string is changed.") is a show stopper for > MSEgui, I can not do more debugging until the problem is solved. Other ways are currently not doable with the current FPC widestring architecture. When does this cause problems? Making assumtions according to memory locations for managed strings is bad anyways?

Type conversion to pwidechar (especially in multi threaded applications) and using watchpoints in GDB. It is almost impossible to debug a system like MSEgui without write-watchpoints. They trigger now on every *read* of an record with OLE-string.

Martin

Reply by email