From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id D11F9393D02A; Tue, 23 Feb 2021 14:59:47 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D11F9393D02A
From: "nilsgladitz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99215] coroutines: debugging with gdb
Date: Tue, 23 Feb 2021 14:59:47 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.2.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nilsgladitz at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-99215-4-e1V2W7iOlQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-99215-4@http.gcc.gnu.org/bugzilla/>
References: <bug-99215-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Feb 2021 14:59:47 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D99215

--- Comment #2 from Nils Gladitz <nilsgladitz at gmail dot com> ---
(In reply to Iain Sandoe from comment #1)
> Can you identify specific key blockers to progress?
> (I think the paper cited contained a number of desiderata, but it would be
> good to start from the most important requirements).

Thank you for the quick reply.

As you and the paper have stated setting breakpoints so far seems to work f=
ine
for me.

What stands out most for me is being unable to inspect parameters (which for
the debugger don't seem to exist) and local variables (their names seem to =
be
known but their values all show as "<optimized out>").

On second look this seems to be only half true as I seem to be able to insp=
ect
both local variables and parameters via the debugger visible "frame_ptr"
variable.

Not straightforward and names seem to be mangled but that might suffice to =
get
started to some degree; won't work with gdb frontends though (which I have =
been
using).

I have no idea of how any of this is actually implemented but I am hoping t=
his
is just a matter of emitting debug information that tells gdb to look for
members and parameters in the corresponding frame_ptr locations?=