public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "khaurbeille+sourceware at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/17632] New: No locals for lambdas in initialiser lists
Date: Fri, 21 Nov 2014 17:04:00 -0000	[thread overview]
Message-ID: <bug-17632-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=17632

            Bug ID: 17632
           Summary: No locals for lambdas in initialiser lists
           Product: gdb
           Version: 7.6
            Status: NEW
          Severity: minor
          Priority: P2
         Component: c++
          Assignee: unassigned at sourceware dot org
          Reporter: khaurbeille+sourceware at gmail dot com

Created attachment 7961
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7961&action=edit
Example code

GDB is not able to display local variables for lambda functions that are used
in an initialiser list. Lambda functions in regular code work fine.

Steps to reproduce:
Compile attached file (GCC 4.8.3) with c++11 and debug info enabled
Run gdb on the executable
Run the following commands:
break 10
break 22
run
info locals
c
info locals

Actual results:
1st info locals:
std::__ioinit = {static _S_refcount = <optimized out>, static
_S_synced_with_stdio = <optimized out>}

2nd info locals:
b = 4
c = @0x7fffffffddac: 4

Expected results:
Similar outputs for the 2 info locals

Stepping works as expected inside both lambdas.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2014-11-21 17:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 17:04 khaurbeille+sourceware at gmail dot com [this message]
2023-12-29 16:59 ` [Bug c++/17632] " ssbssa at sourceware dot org

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-17632-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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: 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).