From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Keven Boell <keven.boell@linux.intel.com>
Cc: Keven Boell <keven.boell@intel.com>,
gdb-patches@sourceware.org, sanimir.agovic@intel.com
Subject: Re: [patch 1/2] Re: Crash regression(?) printing Fortran strings in bt [Re: [V2 00/23] Fortran dynamic array support]
Date: Tue, 12 Aug 2014 21:55:00 -0000 [thread overview]
Message-ID: <20140812215532.GA21463@host2.jankratochvil.net> (raw)
In-Reply-To: <53E9BA7B.1080202@linux.intel.com>
On Tue, 12 Aug 2014 08:55:55 +0200, Keven Boell wrote:
> On 01.08.2014 23:02, Jan Kratochvil wrote:
> > I have it reproducible on Fedora 20 i686 with plain
> > CFLAGS=-g ./configure;make;cd gdb/testsuite;make site.exp;runtest gdb.fortran/dynamic-other-frame.exp
> >
> > Besides that I have updated the testcase with
> > gdb_test_no_output "set print frame-arguments all"
> > so that there is no longer needed the patch:
> > [patch] Display Fortran strings in backtraces
> > https://sourceware.org/ml/gdb-patches/2014-07/msg00709.html
> >
> > The fix below has no regressions for me. Unfortunately I do not see why you
> > cannot reproduce it.
>
> I installed gcc 4.9 on my FC20 32bit system
This is unrelated to gcc 4.9. The problem occurs with standard Fedora 20 i686
compiler which is currently gcc-4.8.3-1.fc20.i686.
I have tried this evening to really reproduce it in 32-bit VM but it does not
happen there, despite all the involved packages are exactly the same build.
IMO it has to depend also on my x86_64 kernel where I run the i686 host in
mock chroot - but I did not try to reproduce it cleanly now.
Providing at least 32-bit build of GDB and its core:
http://people.redhat.com/jkratoch/gdb-bt.tar.xz
It is from the latest Intel vla.git clean commit:
364a416f43095996835d635561e22edceb53d380
> and tried to reproduce the issue like
> you mentioned above. Also this command sequence doesn't give me a crash. However
> I added the patch, which fixes the issue on your end, you mentioned in a different mail
> on the patch series and ran a make check with and without the patch. No regressions
> detected on my system. I've pushed the new series to Github:
> https://github.com/intel-gdb/vla/tree/vla-fortran
The difference of this new branch is only in:
https://github.com/intel-gdb/vla/commit/364a416f43095996835d635561e22edceb53d380
This is a part of:
[patch 2/2] Re: Crash regression(?) printing Fortran strings in bt [Re: [V2 00/23] Fortran dynamic array support]
https://sourceware.org/ml/gdb-patches/2014-08/msg00026.html
but that patch did not fix the bug, it was only trying to add some sanity
checking (which did not work, though).
The fix of the F20 i686 bug was this patch:
[patch 1/2] Re: Crash regression(?) printing Fortran strings in bt [Re: [V2 00/23] Fortran dynamic array support]
https://sourceware.org/ml/gdb-patches/2014-08/msg00025.html
No part of that patch is in the github branch, even not the testcase.
I have verified If I apply the testcase from [patch 1/2] (=the latter one)
GDB still crashes - that is the core file gdb-bt.tar.xz above.
Thanks,
Jan
next prev parent reply other threads:[~2014-08-12 21:55 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 9:21 [V2 00/23] Fortran dynamic array support Keven Boell
2014-07-11 9:21 ` [V2 16/23] test: correct ptype of dynamic arrays in Fortran Keven Boell
2014-07-11 9:21 ` [V2 01/23] dwarf: add dwarf3 DW_OP_push_object_address opcode Keven Boell
2014-07-11 9:21 ` [V2 05/23] vla: make field selection work with vla Keven Boell
2014-07-11 9:21 ` [V2 12/23] vla: add NEWS entry for dynamic array support Keven Boell
2014-07-11 9:58 ` Eli Zaretskii
2014-07-11 9:21 ` [V2 19/23] test: accessing dynamic array history values Keven Boell
2014-07-11 9:21 ` [V2 21/23] test: basic MI test for the dynamic array support Keven Boell
2014-07-11 9:21 ` [V2 08/23] vla: get dynamic array corner cases to work Keven Boell
2014-07-11 9:21 ` [V2 09/23] vla: changed string length semantic Keven Boell
2014-07-18 15:38 ` Jan Kratochvil
2014-07-21 13:23 ` Keven Boell
2014-07-21 19:54 ` Jan Kratochvil
2014-07-22 15:27 ` Keven Boell
2014-07-11 9:22 ` [V2 03/23] vla: introduce allocated/associated flags Keven Boell
2014-07-11 9:22 ` [V2 23/23] test: stride support for dynamic arrays Keven Boell
2014-07-11 9:22 ` [V2 11/23] vla: add stride support to fortran arrays Keven Boell
2014-07-11 9:22 ` [V2 15/23] test: dynamic arrays passed to subroutines Keven Boell
2014-08-01 20:11 ` Jan Kratochvil
2014-08-07 6:58 ` Keven Boell
2014-08-12 6:56 ` Keven Boell
2014-07-11 9:22 ` [V2 22/23] test: test sizeof for dynamic fortran arrays Keven Boell
2014-07-11 9:22 ` [V2 20/23] test: dynamic string evaluations Keven Boell
2014-07-11 9:22 ` [V2 07/23] vla: use value constructor instead of raw-buffer manipulation Keven Boell
2014-07-11 9:22 ` [V2 13/23] test: basic tests for dynamic array evaluations in Fortran Keven Boell
2014-07-11 9:22 ` [V2 18/23] test: dynamic arrays passed to functions Keven Boell
2014-07-11 9:22 ` [V2 17/23] test: evaluating allocation/association status Keven Boell
2014-07-11 9:22 ` [V2 06/23] vla: reconstruct value to compute bounds of target type Keven Boell
2014-07-11 9:22 ` [V2 04/23] vla: make dynamic fortran arrays functional Keven Boell
2014-07-11 9:22 ` [V2 14/23] test: evaluate dynamic arrays using Fortran primitives Keven Boell
2014-07-11 9:22 ` [V2 02/23] dwarf: add DW_AT_data_location support Keven Boell
2014-07-11 9:28 ` [V2 10/23] vla: get Fortran dynamic strings working Keven Boell
2014-07-11 16:23 ` [V2 00/23] Fortran dynamic array support Jan Kratochvil
2014-07-16 16:19 ` Keven Boell
2014-07-16 16:33 ` Jan Kratochvil
2014-07-18 12:33 ` Keven Boell
2014-07-18 15:19 ` Jan Kratochvil
2014-07-29 19:35 ` Crash regression(?) printing Fortran strings in bt [Re: [V2 00/23] Fortran dynamic array support] Jan Kratochvil
2014-07-29 20:51 ` Jan Kratochvil
2014-08-01 7:20 ` Keven Boell
2014-08-01 7:22 ` Jan Kratochvil
2014-08-01 21:02 ` [patch 1/2] " Jan Kratochvil
2014-08-12 6:56 ` Keven Boell
2014-08-12 21:55 ` Jan Kratochvil [this message]
2014-08-14 20:03 ` Jan Kratochvil
2014-08-20 14:09 ` Keven Boell
2014-08-20 18:24 ` Jan Kratochvil
2014-08-21 7:27 ` Keven Boell
2014-08-21 14:29 ` Jan Kratochvil
2014-08-22 7:20 ` Jan Kratochvil
2014-08-01 21:05 ` [patch 2/2] " Jan Kratochvil
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=20140812215532.GA21463@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=keven.boell@intel.com \
--cc=keven.boell@linux.intel.com \
--cc=sanimir.agovic@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