public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Duncan Roe <duncan_roe@optusnet.com.au>
To: cygwin@cygwin.com
Subject: Re: variables, mostly private, not included into debug symbols list on -g3 -ggdb settings
Date: Thu, 30 Jun 2022 10:12:43 +1000	[thread overview]
Message-ID: <Yrzqe4Ksl35/p8JA@slk15.local.net> (raw)
In-Reply-To: <CANeJNHp7xjeqqMDFeST9k14VFPQ=SY1EPqomGtc8nGBqD1bnrQ@mail.gmail.com>

Hi Ariel,

On Thu, Jun 30, 2022 at 12:38:49AM +0200, Ariel Burbaickij wrote:
> Hello list,
> any idea why private variables from  C++ source files are not included into
> symbols list with -g3 and -ggdb compilation settings in gcc version 11.3.0
> under Cygwin. Like that, roughly:
>
> grep isInProgress *
>
> <file_name>:    bool isInProgress;
>
> $nm -Cal <file_name_of_executable>|grep isInProgress
> $
>
> So, watchpoints obviously do not work. Why is it like this ?
>
> Kind Regards
> Ariel Burbaickij
>
I had a similar problem with -g3 -ggdb: macros were not recognised.

Using -g3 -gdwarf4 fixed that for me.

IIUC -ggdb is supposed to select the optimum debug format for gdb. It may be a
bug that it no longer does.

HTH,

Cheers ... Duncan.

  reply	other threads:[~2022-06-30  0:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 22:38 Ariel Burbaickij
2022-06-30  0:12 ` Duncan Roe [this message]
2022-06-30  0:47   ` Ariel Burbaickij

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=Yrzqe4Ksl35/p8JA@slk15.local.net \
    --to=duncan_roe@optusnet.com.au \
    --cc=cygwin@cygwin.com \
    /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).