From: "abdul.b.ijaz via Gdb-patches" <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Cc: abdul.b.ijaz@intel.com
Subject: [PATCH 0/1] Fix variable length strings array for FORTRAN
Date: Fri, 20 Aug 2021 13:06:37 +0200 [thread overview]
Message-ID: <20210820110638.26648-1-abdul.b.ijaz@intel.com> (raw)
Hi All,
GDB is not able to print FORTRAN variable length string array value
when dwarf info contains DW_AT_string_length only regarding the string
length information. So patch update handing of dynamic array for such
cases.
GDB Testsuite is executed using the patch and there is no regression
seen as compare to master on Ubuntu 18.04 machine.
Best Regards,
Abdul Basit
Abdul Basit Ijaz (1):
gdb: Fix arrays of variable length strings for FORTRAN
gdb/c-valprint.c | 1 +
gdb/gdbtypes.c | 12 ++++--
gdb/testsuite/gdb.fortran/vla-array.exp | 57 +++++++++++++++++++++++++
gdb/testsuite/gdb.fortran/vla-array.f90 | 44 +++++++++++++++++++
4 files changed, 110 insertions(+), 4 deletions(-)
create mode 100644 gdb/testsuite/gdb.fortran/vla-array.exp
create mode 100644 gdb/testsuite/gdb.fortran/vla-array.f90
--
2.31.1
next reply other threads:[~2021-08-20 11:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 11:06 abdul.b.ijaz via Gdb-patches [this message]
2021-08-20 11:06 ` [PATCH 1/1] gdb: Fix arrays of variable length strings " abdul.b.ijaz via Gdb-patches
2021-08-20 15:52 ` Andrew Burgess
2021-08-23 8:47 ` Ijaz, Abdul B via Gdb-patches
2021-08-25 8:36 ` Andrew Burgess
2021-08-27 9:11 ` Ijaz, Abdul B via Gdb-patches
2021-08-23 20:54 ` Tom Tromey
2021-08-25 8:56 ` Andrew Burgess
2021-08-27 17:02 ` Tom Tromey
2021-12-29 11:31 ` Ijaz, Abdul B via Gdb-patches
2022-04-11 14:51 ` Ijaz, Abdul B via Gdb-patches
2022-04-15 16:33 ` Tom Tromey
2021-08-20 17:02 ` Andrew Burgess
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=20210820110638.26648-1-abdul.b.ijaz@intel.com \
--to=gdb-patches@sourceware.org \
--cc=abdul.b.ijaz@intel.com \
--cc=abijaz@ecsmtp.iul.intel.com \
/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