Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ruslan Kabatsayev <b7.10110111@gmail.com>
To: noloader@gmail.com
Cc: Christian Biesinger <cbiesinger@google.com>, gdb@sourceware.org
Subject: Re: GDB does not recognize cxx extension?
Date: Sun, 29 Sep 2019 21:23:00 -0000	[thread overview]
Message-ID: <CAHEcG94eUfQdmpsYGzuX4VEt=Rq3rYB_6TysTFpt1vhAB1Z63g@mail.gmail.com> (raw)
In-Reply-To: <CAH8yC8k1vu2bf=hxi6ULrwRTXhrvc18Q_Kq7Ur1F7+=ogCA+iQ@mail.gmail.com>

Hi,

On Sun, 29 Sep 2019 at 08:18, Jeffrey Walton <noloader@gmail.com> wrote:
>
> On Sun, Sep 29, 2019 at 1:09 AM Christian Biesinger
> <cbiesinger@google.com> wrote:
> >
> > On Sun, Sep 29, 2019 at 12:01 AM Jeffrey Walton <noloader@gmail.com> wrote:
> > > I've got a C++ program built from a source called pem_test.cxx. I'm
> > > having trouble getting GDB to accept it. Autocomplete does not work:
> > >
> > >     (gdb) b pem_<TAB>
> > >     pem_common.cpp  pem_common.h    pem_read.cpp    pem_write.cpp
> >
> > GDB gets the list of files from the debug data in the binary, not from
> > the current directory. Are you sure you compiled pem_test.cxx into the
> > binary?
>
> Yes. A 'b main' stops in pem_test.cxx.
>
> The recipe to build pem_test.cxx is at
> https://github.com/noloader/cryptopp-pem/blob/master/pem_create_keys.sh#L42

This line:
"$CXX" "$CXXFLAGS" pem_test.cxx ./libcryptopp.a -o pem_test.exe
passes "-DDEBUG -g3 -O0 -Wall" as a single option. So, it's the same
as -D"DEBUG -g3 -O0 -Wall". Thus the -g3 isn't passed as symbol
generation option. Try removing the quotes.

>
> Jeff

Regards,
Ruslan


      parent reply	other threads:[~2019-09-29 21:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAH8yC8nWS-oFKVOLR1=924a2X_RSwV6j8+keyJHb1tgvqpqEsQ@mail.gmail.com>
2019-09-29  5:09 ` Christian Biesinger via gdb
2019-09-29  5:17   ` Jeffrey Walton
2019-09-29  5:51     ` Christian Biesinger via gdb
2019-09-29  6:49       ` Jeffrey Walton
2019-09-29 15:48         ` Christian Biesinger via gdb
2019-09-29 21:23     ` Ruslan Kabatsayev [this message]

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='CAHEcG94eUfQdmpsYGzuX4VEt=Rq3rYB_6TysTFpt1vhAB1Z63g@mail.gmail.com' \
    --to=b7.10110111@gmail.com \
    --cc=cbiesinger@google.com \
    --cc=gdb@sourceware.org \
    --cc=noloader@gmail.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