This is the mail archive of the
mailing list for the GCC project.
Re: building gcc with macro support for gdb?
- From: Martin Sebor <msebor at gmail dot com>
- To: Tom Tromey <tom at tromey dot com>
- Cc: Peter Bergner <bergner at vnet dot ibm dot com>, Ryan Burn <rnickb731 at gmail dot com>, gcc at gcc dot gnu dot org
- Date: Sat, 05 Dec 2015 10:53:11 -0700
- Subject: Re: building gcc with macro support for gdb?
- Authentication-results: sourceware.org; auth=none
- References: <CACqP_ww+yFuYVZpXZJw+og3Zr776SvpiH1rtqO7SNKjmhm+1+g at mail dot gmail dot com> <1449107325 dot 7269 dot 9 dot camel at vnet dot ibm dot com> <5660674C dot 6050708 at gmail dot com> <87wpsu86gr dot fsf at tromey dot com>
On 12/04/2015 10:32 AM, Tom Tromey wrote:
"Martin" == Martin Sebor <email@example.com> writes:
Martin> To get around these, I end up using info macro to print the
Martin> macro definition and using whatever it expands to instead. I
Martin> wonder if someone has found a more convenient workaround.
For some of these, like the __builtin_offsetof and __null problems, you
can add a new "macro define" to gcc's gdbinit.in.
In fact I already see __null there, so maybe you don't have the correct
add-auto-load-safe-path setting in your ~/.gdbinit.
Yes, thanks. The __null problem is fairly easy to work around
as you suggested. The one that's more difficult is 18881 where
the debugger cannot resolve calls to functions overloaded on
the constness of the argument. Do you happen to have a trick
for dealing with that one?