Sas/c 6.50 map file creation

[hooverphonique]

Hi,

I am trying to compile something with sas/c and would like a map file for debugging purposes.. I just don't seem to have any luck - no file is created.

My question then is: Are the options from SCOPTIONS always read by sc, possibly afterwards being overridden by cmd line options to sc or how does that work? It seems to pick up include directories ok from SCOPTIONS..

in SCOPTIONS, the following mapping options are specified:
MAP
MAPHUNK
MAPLIB
MAPSYMBOLS
MAPFILE=t:out.map

I'm invoking sc through an smakefile, btw..

cheers..

[phx]

Originally Posted by hooverphonique

I am trying to compile something with sas/c and would like a map file for debugging purposes.. I just don't seem to have any luck - no file is created.

My question then is: Are the options from SCOPTIONS always read by sc, possibly afterwards being overridden by cmd line options to sc or how does that work? It seems to pick up include directories ok from SCOPTIONS..

I'm not sure about SCOPTIONS either, and I don't have a recent SAS/C version to verify it. But my guess would be that SCOPTIONS are just passed to the "sc" frontend.

So you could test whether the MAP option works when calling "sc" manually from the command line. If not, it will likely also not work with SCOPTIONS.

Then you can still call slink separately and pass your MAP options there.

[RedskullDC]

Hi Hoover,

Originally Posted by hooverphonique

Hi,

I am trying to compile something with sas/c and would like a map file for debugging purposes.. I just don't seem to have any luck - no file is created.

My question then is: Are the options from SCOPTIONS always read by sc, possibly afterwards being overridden by cmd line options to sc or how does that work? It seems to pick up include directories ok from SCOPTIONS..

in SCOPTIONS, the following mapping options are specified:
MAP
MAPHUNK
MAPLIB
MAPSYMBOLS
MAPFILE=tut.map

I'm invoking sc through an smakefile, btw..

cheers..

Been a while since I looked at SAS/C, so don't take this as gospel...

If invoked from the command line, "sc" will ignore the SCOPTIONS file.

"MAP" will only produce output if you set MAPFILE=filename, select one or more of the map types (hunk,lib etc. as you have above), *AND* choose to "link" as well.

MAP is ignored if "link" is not on the command line, since default is "nolink".

Hope this helps?

Cheers,
Red

p.s. Did you have any luck with your " How does one reverse engineer Amiga app? " problem?

[hooverphonique]

Ahh, I see... the mapping options are of course for linker, not the compiler

SCOPTIONS is perhaps used by smake to set the $SCOPTS variable then.. but my smakefile only has $SCOPTS on the compile steps, not on the link step..

gcc has the ability to create "listing" files.. I don't suppose there's anything similar for sas/c?

@redskull: that thread wasn't started by me

[emufan]

Enable the Hlist, Ilist, and Mlist options. These options cause the compiler to
print, to the listing file, the complete header and macros processed by the
preprocessor

something like that? if so, i found info in this manual.
in version 6.58 there is starter_project/SCoptions. a GUI where you can configure default settings. MAP is also mentioned there.