[fpc-pascal] fpc 2.0 and DOM/xml under OS/2 gives me "Process terminated by SIGSEGV"

Tomas Hajny XHajT03 at mbox.vol.cz
Sat Sep 10 12:03:00 CEST 2005



Date sent:      	Sat, 10 Sep 2005 11:24:16 +0200
From:           	Florian Klaempfl <florian at freepascal.org>
To:             	XHajT03 at vol.cz,
	FPC-Pascal users discussions <fpc-pascal at lists.freepascal.org>
Subject:        	Re: [fpc-pascal] fpc 2.0 and DOM/xml under OS/2 gives me "Process
	terminated by SIGSEGV"

> Tomas Hajny wrote:
> 
> > From:           	Tomas Hajny <XHajT03 at mbox.vol.cz>
> > To:             	FPC-Pascal users discussions
> > <fpc-pascal at lists.freepascal.org> Subject:        	Re: [fpc-pascal]
> > fpc 2.0 and DOM/xml under OS/2 gives me "Process terminated by
> > SIGSEGV" Send reply to:  	XHajT03 at vol.cz Date sent:      	Fri, 9 Sep
> > 2005 23:32:37 +0200
> > 
> > 
> >>>On 21-08-05 15.49, Sřren Ager wrote:
> > 
> >  .
> >  .
> > 
> >>>in dom.pp fixed the problem. So I guess the WideString is broken in
> >>>fpc for OS/2. Is there anyway to disable it so I don't run into
> >>>this problem in the future?
> >>
> >>Sorry, I had your e-mails (together with many other :-( ) in backlog
> >>from the time of my holiday...
> >>
> >>For the first question - the best way to find exact place of SIGSEGV
> >>etc. in FPC programs under OS/2 is to compile everything with debug
> >>information (including RTL, FCL etc.) and either run them under
> >>(PM)GDB, or to open the generated core file in (PM)GDB afterwards
> >>and let it show you the exact location.
> >>
> >>For the second one - I believe that it's a bug in common part of FPC
> >>RTL, in fact, that it crashes when WideString manager is not
> >>initialized. I didn't find time for implementing the OS/2 specific
> >>support for WideString, but it shouldn't crash nevertheless. I'd
> >>suggest to create a simplified test case and add it to our bug
> >>repository so it doesn't get forgotten.
> > 
> > 
> > ...which you already did (at least for the OS/2-specific part), as
> > I've found in the meantime... ;-)
> 
> Fixing this is easy: add a call to initwidestringmanager; in the init
> code of the os2 system unit. It's from rtl/inc/wstrings.inc. This
> pulls in some generic widestring code.

Easy one, indeed, fixed now (at least for this part - there's still 
no platform-specific support added for OS/2, though). It shouldn't 
crash any more.

Tomas




More information about the fpc-pascal mailing list