I am looking to find a way to get the RTL re-compiled so that I can step through it with…
[Charset iso-8859-15 unsupported, skipping...]
[Charset iso-8859-15 unsupported, skipping...]
Huh?

Mailing lists / fpc-devel / 2000-10
9 messages · 6 people · –
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
I am looking to find a way to get the RTL re-compiled so that I can step through it with…
[Charset iso-8859-15 unsupported, skipping...]
[Charset iso-8859-15 unsupported, skipping...]
Huh?
I am looking to find a way to get the RTL re-compiled so that I can step through it with gdb debugger
and look for problems (both in RTL and in applications compiled with RTL) FAQ #31 actually refers to recompiling the RTL with -gl switch.
Currently, I use fpc-1.0.2-i386.rpm to install fpc compiler. Then I use a stripped down Makefile to recompile the RTL source.
That Makefile is attached to this email.
The problem is that normal application builds are causing the RTL pieces to recompile as well. Only executing the Makefile should cause the RTL to compile, not a uses clause in a application unit.
Obviously, the application uses clauses does not allow the appropriate compiler defines and switches to be in used while compiling RTL units.
Some special switches include -Sg and -FE.
Any help appreciated.
[Charset iso-8859-15 unsupported, skipping...] [Charset iso-8859-15 unsupported,…
Hello Marco:
You "Huh?" response sounds like you need further clarification.
Imagine compiling the following program:
program test ;
uses sysutils ;
var
test : string ;
begin
test := 'What am I doing' ;
test := strleft(test,3) ;
end;Now, in gdb, I would like to step down into sysutils.strleft( ) and check out its code as it processes the function call.
Currently, the RTL is not compiled with debug information to allow for stepping into the RTL.
I am looking for a expeditious way to allow this to happen. Notice my uses clause did not say, re-compile
the sysutils unit, just that it wants to link in the function. That linked code should have debugging information
already in it from a makefile I processed earlier.
Make sense now?
Thanks,
Mark
I've raised this 'feature' before & agree that it should be stoppable, but developers said no! but good luck in trying again...John
[Charset iso-8859-15 unsupported, skipping...] [Charset iso-8859-15 unsupported,…
this is just iso-8859-1 plus Euro character; I have elm 2.4 as well on Debian so this seems to be the current version. Strange that -15 isn't supported yet?
- Sebastian
Hello Marco: You "Huh?" response sounds like you need further clarification. Imagine…
Date sent: Mon, 30 Oct 2000 10:47:48 -0500
From: md
To: , ,
Subject: Re: [fpc-devel]RTL debugging
Send reply to:
Hello,
You "Huh?" response sounds like you need further clarification.
.
.
I suspect it had another reason - Marco's client doesn't support the character set specified in your e-mail and filtered everything (except those two lines) out. It isn't your fault though most probably (although I don't know any ISO 8859-15 encoding either). :-)
Have a nice day
Tomas Hajny, on Internet
in urgent cases
this is just iso-8859-1 plus Euro character; I have elm 2.4 as well on Debian so this…
The charsets to be filtered are in elmrc. I wouldn't be surprised if my elmrc is based on a 1993 version :-)
I just finished stuffing all much used charsets (including non official ones like windows-1252) in ELM, and got a little bit edgy when another surfaced. :-)
Marco van de Voort ( or )
The problem is that normal application builds are causing the RTL pieces to recompile as well. Only executing the Makefile should cause the RTL to compile, not a uses clause in a application unit.
To the compiler, the RTL units look no different than any other units. This means that if yyou use -B (build) command line switch, the compiler will recompile all units it can find the full sources for, including the RTL units. To solve this, you simply have to copy the compiled RTL units to another dir (e.g. c:\pp\units\go32v2) and put this unit dir in your -Fu path before the c:\pp\rtl\go32v2 one (or simply remove the latter).
This is what the "make install" command normally does afaik. You should be able to build a normal debugging rtl using the supplied makefiles by issueing the command
make DEBUG=1
Alternatively, you can use
make OPT="-g"
(all parameteres in OPT are directly passed to the compiler)
Jonas
Thanks jonas but I have succeeded at making the RTL completely debuggable
already.
Mark Diener