From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [commit] Remove frame_func_unwind
Date: Sun, 24 Aug 2008 20:29:00 -0000 [thread overview]
Message-ID: <m3hc9acg42.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20080715183655.GA29872@caradoc.them.org> (Daniel Jacobowitz's message of "Tue\, 15 Jul 2008 14\:36\:55 -0400")
>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
Daniel> A number of frame unwind functions are no longer necessary now that
Daniel> unwinders get the current frame. This patch removes
Daniel> frame_func_unwind; tested on x86_64-linux and committed.
Just today I found that this makes --enable-targets=all fail to build
on my x86 F8 box. m88k-tdep.c uses frame_func_unwind, plus a few
other missing things. Error messages appended.
For the time being I just removed m88k-tdep.o from ALL_TARGET_OBS.
Tom
../../src/gdb/m88k-tdep.c: In function ‘m88k_frame_cache’:
../../src/gdb/m88k-tdep.c:660: warning: implicit declaration of function ‘frame_func_unwind’
../../src/gdb/m88k-tdep.c: In function ‘m88k_frame_prev_register’:
../../src/gdb/m88k-tdep.c:731: error: too many arguments to function ‘trad_frame_get_prev_register’
../../src/gdb/m88k-tdep.c:748: error: too many arguments to function ‘trad_frame_get_prev_register’
../../src/gdb/m88k-tdep.c: At top level:
../../src/gdb/m88k-tdep.c:756: warning: initialization from incompatible pointer type
../../src/gdb/m88k-tdep.c: In function ‘m88k_gdbarch_init’:
../../src/gdb/m88k-tdep.c:866: warning: implicit declaration of function ‘set_gdbarch_unwind_dummy_id’
../../src/gdb/m88k-tdep.c:877: warning: implicit declaration of function ‘frame_unwind_append_sniffer’
next prev parent reply other threads:[~2008-08-24 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 18:37 Daniel Jacobowitz
2008-08-24 20:29 ` Tom Tromey [this message]
2008-08-24 21:43 ` Stan Shebs
2008-08-24 22:06 ` Tom Tromey
2008-08-24 22:59 ` Daniel Jacobowitz
2008-08-25 21:06 ` Ulrich Weigand
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=m3hc9acg42.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@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