From: Keven Boell <keven.boell@linux.intel.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>,
Keven Boell <keven.boell@intel.com>
Cc: gdb-patches@sourceware.org, sanimir.agovic@intel.com
Subject: Re: [V2 00/23] Fortran dynamic array support
Date: Wed, 16 Jul 2014 16:19:00 -0000 [thread overview]
Message-ID: <53C69E30.6010902@linux.intel.com> (raw)
In-Reply-To: <20140711160658.GA2366@host2.jankratochvil.net>
Am 11.07.2014 18:06, Jan Kratochvil wrote:
> Hi Keven,
>
> On Fri, 11 Jul 2014 11:21:12 +0200, Keven Boell wrote:
>> Patch series V2 mainly addresses issues/comments given for V1.
>
> this new patchset has crash regressions on Fedora 20 x86_64 for:
> gdb.ada/dyn_arrayidx.exp
> gdb.ada/info_exc.exp
> gdb.ada/mi_exc_info.exp
> and even more gdb.ada/*.exp crashes for i686 and x86_64-m32 runs.
>
I was not able to reproduce the issues on Fedora 20 (64bit and 32bit).
Could you please let me know what compiler you have used?
Tried it with gnat 4.8.3 and it seems to work fine.
> gdb.ada/info_exc.exp
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 0x0000000000812303 in attr_to_dynamic_prop (attr=0x350a008, die=0x3509fd0, cu=0x317ebf0, prop=0x7fff1d6b09a0,
> additional_data=0x0, additional_data_size=0) at dwarf2read.c:14697
> 14697 baton->locexpr.data = DW_BLOCK (attr)->data;
> (gdb) bt
> #0 0x0000000000812303 in attr_to_dynamic_prop (attr=0x350a008, die=0x3509fd0, cu=0x317ebf0, prop=0x7fff1d6b09a0,
> additional_data=0x0, additional_data_size=0) at dwarf2read.c:14697
> #1 0x00000000008126a2 in read_subrange_type (die=0x3509fd0, cu=0x317ebf0) at dwarf2read.c:14799
> #2 0x000000000081acb5 in read_type_die_1 (die=0x3509fd0, cu=0x317ebf0) at dwarf2read.c:18623
> #3 0x000000000081aafc in read_type_die (die=0x3509fd0, cu=0x317ebf0) at dwarf2read.c:18565
> #4 0x000000000080f073 in read_array_type (die=0x3509f50, cu=0x317ebf0) at dwarf2read.c:13515
> #5 0x000000000081ab9d in read_type_die_1 (die=0x3509f50, cu=0x317ebf0) at dwarf2read.c:18593
> #6 0x000000000081aafc in read_type_die (die=0x3509f50, cu=0x317ebf0) at dwarf2read.c:18565
> #7 0x000000000081aa72 in lookup_die_type (die=0x350a0a0, attr=0x350a0d8, cu=0x317ebf0) at dwarf2read.c:18537
> #8 0x000000000081a50e in die_type (die=0x350a0a0, cu=0x317ebf0) at dwarf2read.c:18387
> [...]
>
>
>
> Jan
>
Thanks,
Keven
next prev parent reply other threads:[~2014-07-16 15:46 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 9:21 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 16/23] test: correct ptype of dynamic arrays in Fortran 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 19/23] test: accessing dynamic array history values 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 21/23] test: basic MI test for the " 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 23/23] test: stride support for dynamic arrays Keven Boell
2014-07-11 9:22 ` [V2 03/23] vla: introduce allocated/associated flags Keven Boell
2014-07-11 9:22 ` [V2 17/23] test: evaluating allocation/association status 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 07/23] vla: use value constructor instead of raw-buffer manipulation Keven Boell
2014-07-11 9:22 ` [V2 20/23] test: dynamic string evaluations 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 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 11/23] vla: add stride support to fortran arrays Keven Boell
2014-07-11 9:22 ` [V2 04/23] vla: make dynamic fortran arrays functional 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 02/23] dwarf: add DW_AT_data_location support Keven Boell
2014-07-11 9:22 ` [V2 14/23] test: evaluate dynamic arrays using Fortran primitives 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 [this message]
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
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=53C69E30.6010902@linux.intel.com \
--to=keven.boell@linux.intel.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=keven.boell@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