This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: deprecated_print_frame_info_listing_hook
- From: phi gcc <phi dot gcc at gmail dot com>
- To: gdb at sourceware dot org
- Date: Sun, 20 Jul 2014 11:12:05 +0200
- Subject: Re: deprecated_print_frame_info_listing_hook
- Authentication-results: sourceware.org; auth=none
- References: <CADieKzuUHVjJO2pZuRuPO3_oHpixU0_GtwatKT66vuabaVXyZA at mail dot gmail dot com>
Hi All,
Forget my prev mail, I figured I forgot to setup
deprecated_print_frame_info_listing_hook that is still there.
That raise another question, will it disapear one day ?
Cheers,
Phi
On Sun, Jul 20, 2014 at 10:46 AM, phi gcc <phi.gcc@gmail.com> wrote:
> Hi All,
>
> This is my first post in this ML, if it is not the right place let me
> know and I will register another list.
>
> I have my own hack on gdb since ages, that I port to each new broken
> gdb, I mean each time GDB become incompatible with my updated linux, I
> get the latest GDB and incorporate my few hacks in there. (this may
> happen when [pt]trace change its API)
>
> Today I got from ubuntu LTS 14.04, and my old GDB (6.4) don't work
> anymore. That's ok I get the latest GDB for that ubuntu 14.04 and it
> sounds like it is gdb-7.7, I port my hack in there and kaboom, my hack
> don't port because I heavily depend on
> print_frame_info_listing_hook() to be called upon GDB interaction.
>
> I discover that this print_frame_info_listing_hook() is deprecated (thanx).
>
> My question is, what is the replacement for that, what is the right
> place to stick a callback to my function when we hit a BP and enter
> GDB loop?
>
> Thanx in advance
> Cheers,
> Phi