public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99215] coroutines: debugging with gdb Date: Wed, 24 Feb 2021 15:23:56 +0000 [thread overview] Message-ID: <bug-99215-4-MBF56hnfMG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99215-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215 --- Comment #6 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Nils Gladitz from comment #5) > Apparently when the coroutine happens to be a member function (even a static > one) printing *frame_ptr results in "{<No data fields>}". > > Ideally I'd want to have non-static member coroutines and would like to be > able to inspect the "this" pointer during debugging. .. 'this' gets translated into a reference to the original object for coroutines... hmm have to see if there's any useful advice at this stage. > I was also wondering if "frame_ptr" as a non-reserved name isn't problematic > in case there happens to be e.g. a local variable with that name. the local variables in the ramp are prefixed with 'coro.' which makes them not a legal user identifiers. So it's actually coro.frame_ptr. (where there is potential for clashes, frame variables named are pushed into the implementation space e.g. __ or _CapitalLetter). === I should check in the actor/destroyer if there is scope for a clash (since the variables are local, they are named xxxxxactor:frame_ptr) .. and would be distinct from any var named frame_ptr in the original source .. which would become xxxxxactor:frame_ptr->frame_ptr :) However, when implementing the "idea" described above, I think that might expose the issue - so prefixing with __ or changing the name to _Frame_ptr might be necessary. Of course, I didn't make a test case to prove this, .. but will try it sometime.
next prev parent reply other threads:[~2021-02-24 15:23 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-23 7:29 [Bug c++/99215] New: " nilsgladitz at gmail dot com 2021-02-23 14:21 ` [Bug c++/99215] " iains at gcc dot gnu.org 2021-02-23 14:59 ` nilsgladitz at gmail dot com 2021-02-23 15:26 ` iains at gcc dot gnu.org 2021-02-23 15:53 ` nilsgladitz at gmail dot com 2021-02-24 15:03 ` nilsgladitz at gmail dot com 2021-02-24 15:23 ` iains at gcc dot gnu.org [this message] 2021-03-22 12:13 ` nilsgladitz at gmail dot com 2021-03-22 12:23 ` iains at gcc dot gnu.org 2021-03-22 12:30 ` iains at gcc dot gnu.org 2021-07-09 18:14 ` cvs-commit at gcc dot gnu.org 2021-07-20 6:55 ` cvs-commit at gcc dot gnu.org 2021-09-03 20:25 ` iains at gcc dot gnu.org 2021-10-03 19:28 ` cvs-commit at gcc dot gnu.org 2022-02-15 2:12 ` jarrod.smith at ardentblue dot com
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=bug-99215-4-MBF56hnfMG@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).