public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/96486] get_environment_variable fails for zero-length values
Date: Thu, 06 Aug 2020 16:01:09 +0000 [thread overview]
Message-ID: <bug-96486-4-uuF52RMFF8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96486-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96486
--- Comment #15 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Thu, Aug 06, 2020 at 08:42:20AM +0000, jussilehtola at fedoraproject dot org
wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96486
>
> --- Comment #13 from Susi Lehtola <jussilehtola at fedoraproject dot org> ---
> The gdb output is the same
>
> (gdb) r
> Starting program: /tmp/a.out
> Fortran runtime error: Zero-length string passed as value to
> get_environment_variable.
>
> Error termination. Backtrace:
> #0 0x401267 in zerolen_value
> at /tmp/readvar2.f90:17
> #1 0x4012c4 in main
> at /tmp/readvar2.f90:22
> [Inferior 1 (process 122282) exited with code 02]
>
I cannot reproduce your error. Your original backtrace was
Error termination. Backtrace:
#0 0x7f25c93aadf1 in ???
#1 0x7f25c93ab939 in ???
#2 0x7f25c93abe60 in ???
#3 0x7f25c960ce53 in ???
#4 0x401267 in ???
#5 0x4012c4 in ???
#6 0x7f25c903a041 in __libc_start_main
at ../csu/libc-start.c:308
#7 0x4010ad in ???
#8 0xffffffffffffffff in ???
I would expect a long backtrace under gdb. Don't know
what [Inferior 1...] means.
next prev parent reply other threads:[~2020-08-06 16:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 16:03 [Bug fortran/96486] New: get_environment_variable fails for zero-length variables jussilehtola at fedoraproject dot org
2020-08-05 16:06 ` [Bug fortran/96486] get_environment_variable fails for zero-length values kargl at gcc dot gnu.org
2020-08-05 16:07 ` dominiq at lps dot ens.fr
2020-08-05 16:07 ` dominiq at lps dot ens.fr
2020-08-05 16:42 ` jussilehtola at fedoraproject dot org
2020-08-05 16:43 ` jussilehtola at fedoraproject dot org
2020-08-05 17:36 ` kargl at gcc dot gnu.org
2020-08-05 17:43 ` kargl at gcc dot gnu.org
2020-08-05 17:49 ` kargl at gcc dot gnu.org
2020-08-05 17:53 ` jussilehtola at fedoraproject dot org
2020-08-05 18:00 ` kargl at gcc dot gnu.org
2020-08-05 18:14 ` jussilehtola at fedoraproject dot org
2020-08-05 18:33 ` kargl at gcc dot gnu.org
2020-08-06 8:03 ` markeggleston at gcc dot gnu.org
2020-08-06 8:42 ` jussilehtola at fedoraproject dot org
2020-08-06 15:56 ` sgk at troutmask dot apl.washington.edu
2020-08-06 16:01 ` sgk at troutmask dot apl.washington.edu [this message]
2020-08-06 20:33 ` jussilehtola at fedoraproject dot org
2020-08-07 0:17 ` sgk at troutmask dot apl.washington.edu
2020-08-07 3:02 ` kargl at gcc dot gnu.org
2020-08-07 13:14 ` jussilehtola at fedoraproject dot org
2020-08-07 15:34 ` sgk at troutmask dot apl.washington.edu
2020-08-07 20:35 ` jussilehtola at fedoraproject dot org
2020-08-07 20:36 ` [Bug fortran/96486] get_environment_variable crashes for environment variables that are empty strings jussilehtola at fedoraproject dot org
2020-08-07 20:42 ` jussilehtola at fedoraproject dot org
2020-08-07 21:19 ` sgk at troutmask dot apl.washington.edu
2020-08-07 21:55 ` schwab@linux-m68k.org
2020-08-07 22:13 ` sgk at troutmask dot apl.washington.edu
2020-08-07 22:22 ` harald at gigawatt dot nl
2020-08-08 15:49 ` jussilehtola at fedoraproject dot org
2020-08-24 10:13 ` cvs-commit at gcc dot gnu.org
2020-08-24 11:36 ` cvs-commit at gcc dot gnu.org
2020-08-24 13:51 ` cvs-commit at gcc dot gnu.org
2020-08-24 14:05 ` markeggleston at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-96486-4-uuF52RMFF8@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).