Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Robert Dubner <rdubner@symas.com>
To: <gdb@sourceware.org>
Subject: no attribute '_handle_missing_debuginfo'
Date: Mon, 7 Oct 2024 17:53:53 -0500 (CDT)	[thread overview]
Message-ID: <03e201db190b$c95f1cf0$5c1d56d0$@symas.com> (raw)

I admit defeat, and I throw myself on the mercy of the court.

I really tried.  I searched the internet.  I spent some time digging
through the GDB source code.  But I have been thwarted by the sheer number
of moving parts.

One line background as to why I am compiling GDB:  I am part of an effort
to build a COBOL front end for GCC, and I am making modifications to GDB
to handle the idiosyncracies of COBOL executables.

That said: When I compile and run GDB, I am getting the following
announcement on stderr:

===
Python Exception <class 'AttributeError'>: module 'gdb' has no attribute
'_handle_missing_debuginfo'
===

I believe in my heart that this has to have a simple cause, and I believe
that somewhere there is a switch that can be moved from "broken" to
"fixed" and the message will go away.

But I haven't been able to find it.

I hope some kind soul can embarrass me with a fix.  Go ahead.  I can take
it.

Thanks!

I just now built and compiled the GDB master branch 3f30f11f6d5, which was
committed on 2024-10-07

bob@doobie:~/repos/gdb-cobol/gcobol$ GDB --configuration
This GDB was configured as follows:
   configure --host=x86_64-linux-gnu --target=x86_64-linux-gnu
             --with-auto-load-dir=$debugdir:$datadir/auto-load
             --with-auto-load-safe-path=$debugdir:$datadir/auto-load
             --with-expat
             --with-gdb-datadir=/usr/share/gdb
             --with-jit-reader-dir=/usr/lib/gdb
             --without-libunwind-ia64
             --with-lzma
             --with-babeltrace
             --with-intel-pt
             --with-xxhash
             --with-python=/usr
             --with-python-libdir=/usr/lib
             --with-debuginfod
             --with-curses
             --without-guile
             --without-amd-dbgapi
             --enable-source-highlight
             --enable-threading
             --enable-tui
             --without-system-readline
             --with-separate-debug-dir=/usr/lib/debug
             --with-system-gdbinit=/etc/gdb/gdbinit
             --with-system-gdbinit-dir=/etc/gdb/gdbinit.d

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


             reply	other threads:[~2024-10-07 22:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-07 22:53 Robert Dubner [this message]
2024-10-08  6:13 ` Aktemur, Tankut Baris via Gdb
2024-10-08 18:15   ` Robert Dubner

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='03e201db190b$c95f1cf0$5c1d56d0$@symas.com' \
    --to=rdubner@symas.com \
    --cc=gdb@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