From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Mention signal fixes in NEWS
Date: Mon, 17 May 2004 19:17:00 -0000 [thread overview]
Message-ID: <40A90FC6.7080104@gnu.org> (raw)
In-Reply-To: <3405-Sat15May2004112204+0300-eliz@gnu.org>
Thanks, I'm happy now.
Here's it as committed.
thanks,
Andrew
2004-05-17 Andrew Cagney <cagney@redhat.com>
* NEWS: Mention signal fixes.
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.148
diff -p -u -r1.148 NEWS
--- NEWS 7 May 2004 14:34:35 -0000 1.148
+++ NEWS 17 May 2004 19:14:30 -0000
@@ -3,6 +3,17 @@
*** Changes since GDB 6.1:
+* Signal trampoline code overhauled
+
+Many generic problems with GDB's signal handling code have been fixed.
+These include: backtraces through non-contiguous stacks; recognition
+of sa_sigaction signal trampolines; backtrace from a NULL pointer
+call; backtrace through a signal trampoline; step into and out of
+signal handlers; and single-stepping in the signal trampoline.
+
+These fixes were tested on i386 GNU/Linux systems that include a 2.4
+kernel.
+
* Cygwin support for DWARF 2 added.
* Fixed build problem on IRIX 5
From cagney@gnu.org Mon May 17 19:49:00 2004
From: Andrew Cagney <cagney@gnu.org>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com, freebsd-hackers@freebsd.org, tech-toolchain@netbsd.org
Subject: Re: [PATCH/RFC] *BSD kernel debugging
Date: Mon, 17 May 2004 19:49:00 -0000
Message-id: <40A9172B.9000300@gnu.org>
References: <200405171132.i4HBW0h5012696@elgar.kettenis.dyndns.org>
X-SW-Source: 2004-05/msg00503.html
Content-length: 866
+void
+_initialize_bsd_kvm (void)
+{
+ bsd_kvm_ops.to_shortname = "kvm";
+ bsd_kvm_ops.to_longname = "Kernel memory interface";
+ bsd_kvm_ops.to_doc = "XXX";
+ bsd_kvm_ops.to_open = bsd_kvm_open;
+ bsd_kvm_ops.to_close = bsd_kvm_close;
+ bsd_kvm_ops.to_fetch_registers = bsd_kvm_fetch_registers;
+ bsd_kvm_ops.to_xfer_memory = bsd_kvm_xfer_memory;
+ bsd_kvm_ops.to_stratum = process_stratum;
+ bsd_kvm_ops.to_has_memory = 1;
+ bsd_kvm_ops.to_has_stack = 1;
+ bsd_kvm_ops.to_has_registers = 1;
+ bsd_kvm_ops.to_magic = OPS_MAGIC;
+
+ add_target (&bsd_kvm_ops);
+}
Can the deck chairs be re-arange a little here? Instead of having:
bsd_kvm_supply_pcb
picked up by accident, add an _initialize to the *-nat.c files where
they can do something more explicit vis:
_initialize_foobsd_nat ()
{
add_bsd_kvm_target (foobsd_kvm_supply_pcb);
}
Andrew
prev parent reply other threads:[~2004-05-17 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 19:07 Andrew Cagney
2004-05-12 20:56 ` Daniel Jacobowitz
2004-05-12 21:04 ` Andrew Cagney
2004-05-13 4:52 ` Eli Zaretskii
2004-05-13 18:33 ` Andrew Cagney
2004-05-14 12:38 ` Eli Zaretskii
2004-05-14 15:44 ` Andrew Cagney
2004-05-15 8:23 ` Eli Zaretskii
2004-05-17 19:17 ` Andrew Cagney [this message]
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=40A90FC6.7080104@gnu.org \
--to=cagney@gnu.org \
--cc=eliz@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