From: Tom de Vries <tdevries@suse.de>
To: Hannes Domani <ssbssa@yahoo.de>,
Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2][PR gdb/18706] Calculate size of array of stubbed type
Date: Fri, 1 May 2020 00:01:36 +0200 [thread overview]
Message-ID: <d1c45daf-88c9-0958-89ee-2c2779973e7a@suse.de> (raw)
In-Reply-To: <1035526999.5686211.1588263831423@mail.yahoo.com>
On 30-04-2020 18:23, Hannes Domani via Gdb-patches wrote:
> Am Donnerstag, 30. April 2020, 18:14:26 MESZ hat Simon Marchi <simark@simark.ca> Folgendes geschrieben:
>
>> On 2020-04-30 9:09 a.m., Hannes Domani via Gdb-patches wrote:
>>
>>> Sizes of stubbed types are calculated on demand in check_typedef, so the
>>> same must also be done for arrays of stubbed types.
>>>
>>> A stubbed type is usually a structure that has only been forward declared,
>>> but can also happen if the structure has a virtual function that's not
>>> inline in the class definition.
>>>
>>> For these stubbed types, the size must be recalculated once the full
>>> definition is available.
>>
>>
>> Thanks, this is OK.
>
> Pushed, thanks.
Hi,
This caused:
...
FAIL: gdb.fortran/array-slices.exp: test 2: p array
FAIL: gdb.fortran/array-slices.exp: test 3: p array
FAIL: gdb.fortran/array-slices.exp: test 4: p array
FAIL: gdb.fortran/array-slices.exp: test 5: p array
FAIL: gdb.fortran/array-slices.exp: test 7: p array
FAIL: gdb.fortran/array-slices.exp: test 8: p array
FAIL: gdb.fortran/vla-alloc-assoc.exp: print deallocated vla1
FAIL: gdb.fortran/vla-alloc-assoc.exp: print deallocated vla2
FAIL: gdb.fortran/vla-type.exp: print twov before allocated
FAIL: gdb.fortran/vla-type.exp: print twov%ivla1 before allocated
FAIL: gdb.fortran/vla-ptype.exp: ptype pvla(5, 45, 20) not associated
FAIL: gdb.fortran/vla-ptype.exp: ptype vla1(3, 6, 9) not allocated
FAIL: gdb.fortran/vla-ptype.exp: ptype vla2(5, 45, 20) not allocated
FAIL: gdb.fortran/derived-type-striding.exp: p point_dimension
FAIL: gdb.fortran/derived-type-striding.exp: p point_mixed_dimension
FAIL: gdb.fortran/vla-value-sub.exp: print passed array1 in foo (passed
sub-array)
FAIL: gdb.fortran/vla-value-sub.exp: print array1(5, 5) after filled in
foo (passed sub-array)
FAIL: gdb.fortran/vla-value-sub.exp: print array2 in foo after it was
filled (passed sub-array)
FAIL: gdb.fortran/vla-value-sub.exp: print array2 in foo after it was
mofified in debugger (passed sub-array)
FAIL: gdb.fortran/vla-ptype-sub.exp: ptype array1(3, 3) (passed sub-array)
FAIL: gdb.fortran/vla-ptype-sub.exp: ptype array2(4, 4, 4) (passed
sub-array)
FAIL: gdb.fortran/vla-value.exp: print undefined pvla
FAIL: gdb.fortran/vla-value.exp: print pvla(5, 45, 20) after deassociated
FAIL: gdb.fortran/vla-value.exp: print pvla(7, 45, 14) after dissasociated
FAIL: gdb.fortran/vla-value.exp: print vla1 after deassociated
FAIL: gdb.fortran/vla-value.exp: print allocated vla1(3,6,9) after
specific assignment (deallocated)
FAIL: gdb.fortran/vla-value.exp: print allocated vla1(1,3,8) after
specific assignment (deallocated)
FAIL: gdb.fortran/vla-value.exp: print allocated vla1(9,9,9) after
assignment in debugger (deallocated)
FAIL: gdb.mi/mi-vla-fortran.exp: evaluate not allocated vla, before
allocation (unexpected output)
FAIL: gdb.mi/mi-vla-fortran.exp: eval variable vla1_not_allocated
(unexpected output)
FAIL: gdb.mi/mi-vla-fortran.exp: get children of vla1_not_allocated
(unexpected output)
FAIL: gdb.mi/mi-vla-fortran.exp: evaluate not allocated vla, after
deallocation (unexpected output)
FAIL: gdb.mi/mi-vla-fortran.exp: evaluate vla pointer set to null
(unexpected output)
...
Thanks,
- Tom
prev parent reply other threads:[~2020-04-30 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200430130954.15121-1-ssbssa.ref@yahoo.de>
2020-04-30 13:09 ` Hannes Domani
2020-04-30 16:14 ` Simon Marchi
2020-04-30 16:23 ` Hannes Domani
2020-04-30 22:01 ` Tom de Vries [this message]
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=d1c45daf-88c9-0958-89ee-2c2779973e7a@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=ssbssa@yahoo.de \
/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