. The version of strings included in GNU
binutils searches for strings terminated by any non-printable
character, so it finds Fortran style strings (and a lot of noise which
isn't strings).
Op vr 3 jun. 2022 om 09:25 schreef Kay Diederichs <
kay.diederi...@uni-konstanz.de>:
@Janne thanks for po
Am 02.06.22 um 21:06 schrieb Janne Blomqvist:
On Wed, Jun 1, 2022 at 1:16 PM Kay Diederichs
wrote:
If -g is used, the executable _always_ has version and option info
Well, isn't that the answer to your question then?
As an alternative approach, make a command-line option (say, &qu
around might be to compile one source file containing this
code with -g, but that is pushing things to the limit.
Regards,
Arjen
Op wo 1 jun. 2022 om 12:16 schreef Kay Diederichs mailto:kay.diederi...@uni-konstanz.de>>:
I tried your suggestion below, but it do
()
d = compiler_options()
write(*,*) c(1:1), d(1:)1
end program staticv
--
Kay Diederichshttp://strucbio.biologie.uni-konstanz.de
email: kay.diederi...@uni-konstanz.de Tel +49 7531 88 4049
Fachbereich Biologie, Universität Konstanz, Box M647, D-78457 Konstanz
WRITE( lurep, '(a)' ) 'Compiler options: ', compiler_options()
Regards,
Arjen
Op wo 1 jun. 2022 om 10:42 schreef Kay Diederichs mailto:kay.diederi...@uni-konstanz.de>>:
Hi,
is there any gfortran option and/or version information available from/in a
binary? Maybe accessi
Hi,
is there any gfortran option and/or version information available from/in a
binary? Maybe accessible with objdump or strings?
For ifort, we use the -sox option ("This option tells the compiler to save the
compilation options and version number in the executable file. ..."). This enables
On 3/10/21 12:35 PM, Martin Stein via Fortran wrote:
> Hi,
>
> I am seeing rare but reproducible memory corruptions which I can trace back
> to lines like
>
> write(out,'(a,i8)') 'short string', k
>
> where out is a (sufficiently large) character(len=...) variable and k some
> small integer.
