Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com, cagney@redhat.com
Subject: Re: [Fwd: gcore for netbsd]
Date: Mon, 05 Aug 2002 21:19:00 -0000	[thread overview]
Message-ID: <3D4F4E3B.4010801@ges.redhat.com> (raw)
In-Reply-To: <3D4F023B.A6B5BD9@redhat.com>

> Andrew Cagney wrote:
> 
>> 
>> Hello,
>> 
>> This patch has made me wonder why gcore even includes <sys/procfs.h>.
> 
> 
> I'm guessing it went in before I split some code out into linux-proc.c.
> 
> 
> 
>> Can anyone think of a reason for not simply removing the include?
> 
> 	
> Try it and see...

Going going ....

>> I'm also wondering what the function preempt_derive_stack_segment() is
>> for.  I can't find any callers.
> 
> 
> Probably for future use -- for systems where the default method didn't 
> work, or where there was a more efficient method available.

It can't be a global though.  That is going to be very multi-arch / 
multi-target unfriendly.

Mind if that gets removed as well?  As it is, it is wrong.

Andrew


>>   ------------------------------------------------------------------------
>> 
>> Subject: gcore for netbsd
>> Date: 16 Jul 2002 03:35:47 +0200
>> From: Love <lha@stacken.kth.se>
>> To: gdb@sources.redhat.com
>> 
>> 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"
>>
> 
> 



  reply	other threads:[~2002-08-06  4:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-04 11:02 Andrew Cagney
2002-08-05 16:13 ` Michael Snyder
2002-08-05 21:19   ` Andrew Cagney [this message]
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=3D4F4E3B.4010801@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=cagney@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --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