public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: fortran@gcc.gnu.org, kargl@gcc.gnu.org
Subject: Re: co-arrays and libgfortran
Date: Tue, 22 Dec 2020 14:22:19 -0800	[thread overview]
Message-ID: <20201222222219.GA55719@troutmask.apl.washington.edu> (raw)
In-Reply-To: <20201222220847.GA34647@troutmask.apl.washington.edu>

On Tue, Dec 22, 2020 at 02:08:47PM -0800, Steve Kargl wrote:
> More monologuing.
> 
> I copied gcc/testsuite/gfortran.dg/caf-shared/dummy_1.f90 to tmp/dummy_1.f90.
> 
> % gfccas -o z dummy_1.f90 
> % ./z
> ERROR: Image 2(0x1748) failed
> % ps | grep z
>  5958  1  I    0:00.00 ./z
>  5959  1  I    0:00.00 ./z
>  5963  1  S+   0:00.01 grep z
> % kill 5959
> ERROR: Image 2(0x1747) failed
> 

Recompiled with -g and the image dropped core.

% gdb ./z z.core

Core was generated by `./z'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  scan_inside_lookahead (id=134523584, expected_off=<optimized out>, 
    hm=0x281c2198) at ../../../cas/libgfortran/caf_shared/hashmap.c:157
157       lookahead = data[expected_off].max_lookahead;
(gdb) bt
#0  scan_inside_lookahead (id=134523584, expected_off=<optimized out>, 
    hm=0x281c2198) at ../../../cas/libgfortran/caf_shared/hashmap.c:157
#1  hashmap_get (hm=0x281c2198, id=134523584)
    at ../../../cas/libgfortran/caf_shared/hashmap.c:196
#2  0x2808d002 in get_memory_by_id_internal (iface=0x281c2188, size=8, 
    id=134523584, zero_mem=false)
    at ../../../cas/libgfortran/caf_shared/alloc.c:55
#3  0x2808ed9f in _gfortran_cas_coarray_alloc (desc=0x804aac0 <b>, 
    elem_size=4, corank=1, alloc_type=1)
    at ../../../cas/libgfortran/caf_shared/wrapper.c:154
#4  0x08048dbe in MAIN__ () at dummy_1.f90:30
(gdb) up 1
#1  hashmap_get (hm=0x281c2198, id=134523584)
    at ../../../cas/libgfortran/caf_shared/hashmap.c:196
196       res = scan_inside_lookahead (hm, expected_offset, id);
(gdb) p *hm
$1 = {s = 0x281ef0bc, sm = 0x281c2184, a = 0x281c2190}
(gdb) p *hm->s
$2 = {data = {offset = 208}, size = 32, bitnum = 5}
(gdb) p *hm->sm
$3 = (shared_memory) 0x2808a020
(gdb) p **hm->sm
$4 = {meta = 0x281ef000, header = 0x0, last_seen_size = 4096, 
  num_local_allocs = 1, allocs = 0x2808a030}
(gdb) p *hm->a
$5 = {s = 0x281ef03c, shm = 0x281c2184}
(gdb) p *hm->a->s
$6 = {free_bucket_head = {{offset = -1} <repeats 32 times>}}
(gdb) p *hm->a->shm
$7 = (shared_memory) 0x2808a020
(gdb) p **hm->a->shm
$8 = {meta = 0x281ef000, header = 0x0, last_seen_size = 4096, 
  num_local_allocs = 1, allocs = 0x2808a030}

Any of this look familiar?

-- 
Steve

  reply	other threads:[~2020-12-22 22:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18  4:28 Steve Kargl
2020-12-18 12:26 ` Thomas Koenig
2020-12-18 15:52   ` Steve Kargl
2020-12-19 21:59     ` Steve Kargl
2020-12-20 10:52       ` Thomas Koenig
2020-12-20 17:47         ` Steve Kargl
2020-12-21  1:04           ` Steve Kargl
2020-12-21  2:01             ` Damian Rouson
2020-12-21 13:15     ` Thomas Koenig
2020-12-21 15:18       ` Steve Kargl
2020-12-21 23:44         ` Thomas Koenig
2020-12-22  0:18           ` Steve Kargl
2020-12-22  1:40             ` Steve Kargl
2020-12-22 10:04               ` Thomas Koenig
2020-12-22 18:32                 ` Steve Kargl
2020-12-22 19:33                   ` Steve Kargl
2020-12-22 20:12                     ` Steve Kargl
2020-12-22 20:20                       ` Steve Kargl
2020-12-22 22:08                         ` Steve Kargl
2020-12-22 22:22                           ` Steve Kargl [this message]
2020-12-22 23:24               ` Steve Kargl
2020-12-22 23:46                 ` Thomas Koenig

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=20201222222219.GA55719@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=fortran@gcc.gnu.org \
    --cc=kargl@gcc.gnu.org \
    --cc=tkoenig@netcologne.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).