From: "Christian Biesinger via gdb" <gdb@sourceware.org>
To: noloader@gmail.com
Cc: gdb@sourceware.org
Subject: Re: GDB does not recognize cxx extension?
Date: Sun, 29 Sep 2019 05:51:00 -0000 [thread overview]
Message-ID: <CAPTJ0XH82z4=vNj5sAgTfASeoLO_9AdsMsBFiE-s=OdOfB0fRg@mail.gmail.com> (raw)
In-Reply-To: <CAH8yC8k1vu2bf=hxi6ULrwRTXhrvc18Q_Kq7Ur1F7+=ogCA+iQ@mail.gmail.com>
On Sun, Sep 29, 2019 at 12:17 AM 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
So, GDB does know that cxx is an extension for C++:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=gdb/c-lang.c;h=57592dfbce0f8822fa3ca3d68ed520b4124a0c5d;hb=612aac65e690387c963c34a31dd1fb138d88a45c#l1032
And .cxx does work for me:
Reading symbols from ./test...
(gdb) break test.cxx:2
Breakpoint 1 at 0x1129: file test.cxx, line 2.
(gdb) r
Starting program: /tmp/test
Breakpoint 1, main () at test.cxx:2
2 return 42;
(gdb) b test<TAB>
std::__atomic0::atomic_flag::test_and_set(std::memory_order) test.cxx
There must be something odd about your build setup, but I don't know
what it is. For testing purposes, if you build the cxx as part of your
static library, does it work?
Christian
next prev parent reply other threads:[~2019-09-29 5:51 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 [this message]
2019-09-29 6:49 ` Jeffrey Walton
2019-09-29 15:48 ` Christian Biesinger via gdb
2019-09-29 21:23 ` Ruslan Kabatsayev
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='CAPTJ0XH82z4=vNj5sAgTfASeoLO_9AdsMsBFiE-s=OdOfB0fRg@mail.gmail.com' \
--to=gdb@sourceware.org \
--cc=cbiesinger@google.com \
--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