Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: phi gcc <phi.gcc@gmail.com>
To: gdb@sourceware.org
Subject: deprecated_print_frame_info_listing_hook
Date: Sun, 20 Jul 2014 08:46:00 -0000	[thread overview]
Message-ID: <CADieKzuUHVjJO2pZuRuPO3_oHpixU0_GtwatKT66vuabaVXyZA@mail.gmail.com> (raw)

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


             reply	other threads:[~2014-07-20  8:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-20  8:46 phi gcc [this message]
2014-07-20  9:12 ` deprecated_print_frame_info_listing_hook phi gcc
2014-07-21 19:56   ` deprecated_print_frame_info_listing_hook Tom Tromey
2014-07-31  6:55     ` deprecated_print_frame_info_listing_hook phi gcc

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=CADieKzuUHVjJO2pZuRuPO3_oHpixU0_GtwatKT66vuabaVXyZA@mail.gmail.com \
    --to=phi.gcc@gmail.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