From: Andrew Cagney <ac131313@ges.redhat.com>
To: gdb-patches@sources.redhat.com, Michael Snyder <msnyder@redhat.com>
Cc: lha@stacken.kth.se
Subject: [Fwd: gcore for netbsd]
Date: Sun, 04 Aug 2002 11:02:00 -0000 [thread overview]
Message-ID: <3D4D6C36.8050407@ges.redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 261 bytes --]
Hello,
This patch has made me wonder why gcore even includes <sys/procfs.h>.
Can anyone think of a reason for not simply removing the include?
--
I'm also wondering what the function preempt_derive_stack_segment() is
for. I can't find any callers.
Andrew
[-- Attachment #2: gcore for netbsd --]
[-- Type: message/rfc822, Size: 3086 bytes --]
From: Love <lha@stacken.kth.se>
To: gdb@sources.redhat.com
Subject: gcore for netbsd
Date: 16 Jul 2002 03:35:47 +0200
Message-ID: <amd6totpxo.fsf@sul.e.kth.se>
Hi
I've added gcore support for netbsd, the core writing support need some
more work (like adding more stuff to the elf notes in the netbsd core file)
One simple thing you can do for me is to protect the <sys/procfs.h> in
gcore.c like its done in other files so its possible to include gcore.c on
platforms that doesn't have <sys/procfs.h>.
Love
Index: gcore.c
===================================================================
RCS file: /cvs/src/src/gdb/gcore.c,v
retrieving revision 1.5
diff -u -u -w -r1.5 gcore.c
--- gcore.c 12 Apr 2002 23:09:48 -0000 1.5
+++ gcore.c 16 Jul 2002 01:30:03 -0000
@@ -23,7 +23,9 @@
#include "inferior.h"
#include "gdbcore.h"
#include "elf-bfd.h"
+#ifdef HAVE_SYS_PROCFS_H
#include <sys/procfs.h>
+#endif
#include "symfile.h"
#include "objfiles.h"
next reply other threads:[~2002-08-04 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 11:02 Andrew Cagney [this message]
2002-08-05 16:13 ` Michael Snyder
2002-08-05 21:19 ` Andrew Cagney
2002-08-05 21:39 ` Michael Snyder
2002-08-06 8:53 ` Andrew Cagney
2002-08-06 10:39 ` Love
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=3D4D6C36.8050407@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=lha@stacken.kth.se \
--cc=msnyder@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