Hello,

can you tell me why
- OPTLINK 7.50B1 writes '7.80' as the linker version into the executables?
- this version of the linker generates an (empty) .debug section even if
there's no debugging information?

Thanks,
Matthias.

What kind of executable are you building?

"Matthias Stemmler" <m.stemmler@t-online.de> wrote in message news:abovjj$1sf6$1@digitaldaemon.com...
> Hello,
>
> can you tell me why
> - OPTLINK 7.50B1 writes '7.80' as the linker version into the executables?
> - this version of the linker generates an (empty) .debug section even if
> there's no debugging information?
>
> Thanks,
> Matthias.
>
>

/EXETYPE:NT, applies to both console and GUI.

Thanks.

"Walter" <walter@digitalmars.com> schrieb im Newsbeitrag news:abqc8g$5i$1@digitaldaemon.com...
> What kind of executable are you building?
>
> "Matthias Stemmler" <m.stemmler@t-online.de> wrote in message news:abovjj$1sf6$1@digitaldaemon.com...
> > Hello,
> >
> > can you tell me why
> > - OPTLINK 7.50B1 writes '7.80' as the linker version into the
executables?
> > - this version of the linker generates an (empty) .debug section even if there's no debugging information?
> >
> > Thanks,
> > Matthias.
> >
> >
>
>

Ok, I just checked and don't see a '7.80' embedded into the exe file. Which PE record do you see it in?

"Matthias Stemmler" <m.stemmler@t-online.de> wrote in message news:abqtbo$h0e$1@digitaldaemon.com...
> /EXETYPE:NT, applies to both console and GUI.
>
> Thanks.
>
> "Walter" <walter@digitalmars.com> schrieb im Newsbeitrag news:abqc8g$5i$1@digitaldaemon.com...
> > What kind of executable are you building?
> >
> > "Matthias Stemmler" <m.stemmler@t-online.de> wrote in message news:abovjj$1sf6$1@digitaldaemon.com...
> > > Hello,
> > >
> > > can you tell me why
> > > - OPTLINK 7.50B1 writes '7.80' as the linker version into the
> executables?
> > > - this version of the linker generates an (empty) .debug section even
if
> > > there's no debugging information?
> > >
> > > Thanks,
> > > Matthias.
> > >
> > >
> >
> >
>
>

It's in the optional header, just after the 'magic' 0x010b. The field 'MajorLinkerVersion' is correctly set to 0x07 but the following 'MinorLinkerVersion' shows 0x50, which should be 0x32 unless the linker version 7.50 is meant to be a hex number. But this doesn't make sense because every PE inspection program will show '7.80' and thus lead to confusion (at least for me).

And what about the '.debug' section I mentioned before?
By the way, the file 'sc.exe' from DMC++ v827.5 is such an executable.

Thanks a lot,
Matthias.

"Walter" <walter@digitalmars.com> schrieb im Newsbeitrag news:abrcaa$tlf$1@digitaldaemon.com...
> Ok, I just checked and don't see a '7.80' embedded into the exe file.
Which
> PE record do you see it in?
>
> "Matthias Stemmler" <m.stemmler@t-online.de> wrote in message news:abqtbo$h0e$1@digitaldaemon.com...
> > /EXETYPE:NT, applies to both console and GUI.
> >
> > Thanks.
> >
> > "Walter" <walter@digitalmars.com> schrieb im Newsbeitrag news:abqc8g$5i$1@digitaldaemon.com...
> > > What kind of executable are you building?
> > >
> > > "Matthias Stemmler" <m.stemmler@t-online.de> wrote in message news:abovjj$1sf6$1@digitaldaemon.com...
> > > > Hello,
> > > >
> > > > can you tell me why
> > > > - OPTLINK 7.50B1 writes '7.80' as the linker version into the
> > executables?
> > > > - this version of the linker generates an (empty) .debug section
even
> if
> > > > there's no debugging information?
> > > >
> > > > Thanks,
> > > > Matthias.
> > > >
> > > >
> > >
> > >
> >
> >
>
>

"Matthias Stemmler" <m.stemmler@t-online.de> wrote in message news:abrgjf$11av$1@digitaldaemon.com...
> It's in the optional header, just after the 'magic' 0x010b. The field 'MajorLinkerVersion' is correctly set to 0x07 but the following 'MinorLinkerVersion' shows 0x50, which should be 0x32 unless the linker version 7.50 is meant to be a hex number. But this doesn't make sense because every PE inspection program will show '7.80' and thus lead to confusion (at least for me).

Ok, I see it. And yes, it is in hex. Ironically, the Digital Mars PE inspection program (dumpexe) will show it in hex.

> And what about the '.debug' section I mentioned before?

It doesn't matter, since it is small and doesn't get loaded anyway.