Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Robert Dubner <rdubner@symas.com>
To: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>,
	<gdb@sourceware.org>
Subject: RE: no attribute '_handle_missing_debuginfo'
Date: Tue, 8 Oct 2024 13:15:58 -0500 (CDT)	[thread overview]
Message-ID: <057b01db19ae$1fd665f0$5f8331d0$@symas.com> (raw)
In-Reply-To: <DM4PR11MB7303755E5044C71484E79ACBC47E2@DM4PR11MB7303.namprd11.prod.outlook.com>

Baris, thank you for responding.

Your speculation is correct; GDB is my alias to the
"<build_folder>/gdb/gdb" executable in my build tree.  I am in the
position of using the system-installed 'gdb' to debug my locally-built
gdb, so for now I don't want to install the locally-built version.

Your suggestion was accurate.  My locally-built GDB was using the
/usr/share/gdb data directory of the system-installed gdb-12.1

When I specify --data-directory as you described, the " no attribute
'_handle_missing_debuginfo'" message no longer appears.

Fun fact: When --data-directory=misspelled-directory-path is used, a
number of new and exciting error messages appear!

Thank you so much for taking the time to answer my question.

Bob Dubner

> -----Original Message-----
> From: Aktemur, Tankut Baris <tankut.baris.aktemur@intel.com>
> Sent: Tuesday, October 8, 2024 02:14
> To: Robert Dubner <rdubner@symas.com>; gdb@sourceware.org
> Subject: RE: no attribute '_handle_missing_debuginfo'
> 
> On Tuesday, October 8, 2024 12:54 AM, Robert Dubner wrote:
> > bob@doobie:~/repos/gdb-cobol/gcobol$ GDB --version GNU gdb (GDB-COBOL
> > 14.0.7 (debuggable)) 16.0.50.20241007-git
> >
> > bob@doobie:~/repos/gdb-cobol/gcobol$ GDB -q
> > (gdb) python
> > >print(sys.version)
> > >end
> > 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0]
> >
> > (gdb) file ctest
> > Reading symbols from ctest...
> > (gdb) start
> > Temporary breakpoint 1 at 0x122a: file ctest.c, line 19.
> > Starting program: /home/bob/repos/gdb-cobol/gcobol/ctest
> > Python Exception <class 'AttributeError'>: module 'gdb' has no
> > attribute '_handle_missing_debuginfo'
> > [Thread debugging using libthread_db enabled] Using host libthread_db
> > library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> >
> > Temporary breakpoint 1, main (argc=1, argv=0x7fffffffe328) at
> > ctest.c:19
> 
> What is 'GDB' in the commands above?  Is it an alias to the gdb binary
in
> your build folder?  If you're using your locally-built gdb binary from
the
> build folder and not the install folder, please try passing the data-
> directory flag.  Otherwise, a data-directory in a more default location
> takes precedence.
> 
>   $ /<path-to-build-folder>/gdb/gdb -q --data-directory=/<path-to-build-
> folder>/gdb/data-directory
> 
> You can run the "show data-directory" command to check if it is pointing
> to the right folder.
> 
> -Baris
> 
> 
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0, www.intel.de
> Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon
> Silva Chairperson of the Supervisory Board: Nicole Lau Registered
Office:
> Munich Commercial Register: Amtsgericht Muenchen HRB 186928


      reply	other threads:[~2024-10-08 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-07 22:53 Robert Dubner
2024-10-08  6:13 ` Aktemur, Tankut Baris via Gdb
2024-10-08 18:15   ` Robert Dubner [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='057b01db19ae$1fd665f0$5f8331d0$@symas.com' \
    --to=rdubner@symas.com \
    --cc=gdb@sourceware.org \
    --cc=tankut.baris.aktemur@intel.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