From: Andrew Cagney <cagney@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: [ob] Add missing #include gdb_assert.h
Date: Tue, 11 May 2004 16:17:00 -0000 [thread overview]
Message-ID: <40A0FCA2.6030809@gnu.org> (raw)
committed,
Andrew
2004-05-11 Andrew Cagney <cagney@redhat.com>
* ppcnbsd-tdep.c: Include "gdb_assert.h".
* Makefile.in (ppcnbsd-tdep.o): Update dependencies.
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/Makefile.in,v
retrieving revision 1.569
diff -p -u -r1.569 Makefile.in
--- Makefile.in 11 May 2004 04:55:31 -0000 1.569
+++ Makefile.in 11 May 2004 16:15:08 -0000
@@ -2162,7 +2162,7 @@ ppcnbsd-nat.o: ppcnbsd-nat.c $(defs_h) $
$(ppcnbsd_tdep_h) $(gdb_assert_h)
ppcnbsd-tdep.o: ppcnbsd-tdep.c $(defs_h) $(gdbcore_h) $(regcache_h) \
$(target_h) $(breakpoint_h) $(value_h) $(osabi_h) $(ppc_tdep_h) \
- $(ppcnbsd_tdep_h) $(nbsd_tdep_h) $(solib_svr4_h)
+ $(ppcnbsd_tdep_h) $(nbsd_tdep_h) $(solib_svr4_h) $(gdb_assert)
ppcobsd-nat.o: ppcobsd-nat.c $(defs_h) $(inferior_h) $(regcache_h) \
$(ppc_tdep_h) $(ppcobsd_tdep_h)
ppcobsd-tdep.o: ppcobsd-tdep.c $(defs_h) $(arch_utils_h) $(osabi_h) \
Index: ppcnbsd-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/ppcnbsd-tdep.c,v
retrieving revision 1.19
diff -p -u -r1.19 ppcnbsd-tdep.c
--- ppcnbsd-tdep.c 11 May 2004 04:55:32 -0000 1.19
+++ ppcnbsd-tdep.c 11 May 2004 16:15:08 -0000
@@ -34,7 +34,7 @@
#include "nbsd-tdep.h"
#include "tramp-frame.h"
#include "trad-frame.h"
-
+#include "gdb_assert.h"
#include "solib-svr4.h"
#define REG_FIXREG_OFFSET(x) ((x) * 4)
From cagney@gnu.org Tue May 11 16:30:00 2004
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: Mark Kettenis <kettenis@chello.nl>, gdb-patches@sources.redhat.com, roland@redhat.com
Subject: Re: [obish?sym;rfa:doc] Wire up vsyscall
Date: Tue, 11 May 2004 16:30:00 -0000
Message-id: <40A0FFB1.8030407@gnu.org>
References: <409A8C2A.2010605@gnu.org> <409AA61F.8050807@gnu.org> <20040507012549.GA30182@nevyn.them.org> <409FF3D7.5000106@gnu.org> <200405102140.i4ALe13A001092@elgar.kettenis.dyndns.org> <20040511145344.GA15501@nevyn.them.org>
X-SW-Source: 2004-05/msg00336.html
Content-length: 368
To what extent do we need to know about SIGTRAMP_FRAME for other
purposes? I guess we need it to get stepping into/through signal
trampolines working properly, but I'd like to be certain about it.
I'm not sure we'll need it for that also. Maybe, but no reason jumps
out at me.
Er, infrun single-steps through trampolines rather than skipping over them.
Andrew
next reply other threads:[~2004-05-11 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 16:17 Andrew Cagney [this message]
2004-05-11 20:52 ` Jim Blandy
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=40A0FCA2.6030809@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.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