From: Tom Tromey <tromey@redhat.com>
To: phi gcc <phi.gcc@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: deprecated_print_frame_info_listing_hook
Date: Mon, 21 Jul 2014 19:56:00 -0000 [thread overview]
Message-ID: <87ppgyscy8.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CADieKzsCZFMXdsm6GENPLv36FHJ=6GKoL_Ee0PZvPanihyixtw@mail.gmail.com> (phi gcc's message of "Sun, 20 Jul 2014 11:12:05 +0200")
>>>>> "Phi" == phi gcc <phi.gcc@gmail.com> writes:
Phi> Forget my prev mail, I figured I forgot to setup
Phi> deprecated_print_frame_info_listing_hook that is still there.
You never said what your hack is.
That makes it hard to give advice.
Phi> That raise another question, will it disapear one day ?
Probably.
Tom
next prev parent reply other threads:[~2014-07-21 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 8:46 deprecated_print_frame_info_listing_hook phi gcc
2014-07-20 9:12 ` deprecated_print_frame_info_listing_hook phi gcc
2014-07-21 19:56 ` Tom Tromey [this message]
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=87ppgyscy8.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=phi.gcc@gmail.com \
/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