Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Gutson <dgutson@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
	  "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gcore fix for native gdb on solaris
Date: Tue, 12 Jan 2010 21:44:00 -0000	[thread overview]
Message-ID: <4B4CED3C.80206@codesourcery.com> (raw)
In-Reply-To: <20100112132335.GN2007@adacore.com>

Hi Joel,

Joel Brobecker wrote:
>> I was not somehow sure whether it is expected and I also wanted to make some
>> heads-up whether _STRUCTURED_PROC #defines aren't now obsoleted in proc*.c
>> files (I do not know if they are or not).
> 
> It isn't, as far as I know. I thought I had seen on Solaris 10
> that _STRUCTURED_PROC was always assumed, but upon double-checking,
> it appears not so.  In any case, the only risk is with old versions
> of Solaris where _STRUCTURED_PROC is ignored - we might have a build
> failure because we expected to have elfcore_write_lwpstatus, whereas
> bfd only provided elfcore_write_lpstatus... I doubt it; my guess is
> NEW_PROC_API would not be defined on these systems.
> 

I'm becoming up to date with this thread.
Is there anything pending from me to do, any commit, any validation?
FWIW, I already checked it for sparc-solaris.

Thanks!
	Daniel.

-- 
Daniel Gutson
CodeSourcery
www.codesourcery.com


  reply	other threads:[~2010-01-12 21:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 22:14 Daniel Gutson
2009-11-11 15:04 ` Tom Tromey
2010-01-05  0:52   ` Daniel Gutson
2010-01-05 17:51     ` Tom Tromey
2010-01-09  5:05 ` Joel Brobecker
2010-01-11 16:28 ` Jan Kratochvil
2010-01-12  3:39   ` Joel Brobecker
2010-01-12 12:27     ` Jan Kratochvil
2010-01-12 13:23       ` Joel Brobecker
2010-01-12 21:44         ` Daniel Gutson [this message]
2010-01-12 22:03           ` Jan Kratochvil
2010-01-12 23:57             ` Daniel Gutson

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=4B4CED3C.80206@codesourcery.com \
    --to=dgutson@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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