Home/ Questions/Q 7975091
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T08:33:16+00:00

I use the apple’s gdb, version as follow GNU gdb 6.3.50-20050815 (Apple version gdb-1344)

  • 0

I use the apple’s gdb, version as follow

GNU gdb 6.3.50-20050815 (Apple version gdb-1344) (Fri Jul  3 01:19:56 UTC 2009)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-apple-darwin".

I don’t use Xcode IDE since for my needs makefile-managed projects are more convenient, especially because I often need to compile and run programs on remote machines. I have recently started to use the following c++11 features (on g++-4.6 and 4.7 from macports): move constructors, nullptr, auto and decltype. I rencently needed to d3bug my code, and the following weird message appeared instead of stepping into a function:

Die: DW_TAG_unspecified_type (abbrev = 36, offset = 4315)
        has children: FALSE
        attributes:
                DW_AT_name (DW_FORM_string) string: "decltype(nullptr)"

from since this message appears, all following gdb commands are answered by the same weird message, so it is not possible to debug anymore. It seems something related to c++11. My question is, have you ever encountered this message, and how to get rid
of it?

Thanks in advance

Giuliano

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The version of GDB you’re using (Apple’s version) doesn’t seem to support the newer features of the compiler you installed from macports.

    The error message is reporting that GDB doesn’t understand some of the debugging information it’s encountered in the program. The debugging information it has shown is a C++11 feature.

    The solution is to either upgrade to a newer GDB (probably from macports if there’s one there), not use the features that GDB doesn’t understand, or accept that the version of GDB you have won’t be able to understand this.

    • 0