Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Makefile.in, linux.mh: Move Process Record to NATDEPFILES
Date: Sun, 25 Oct 2009 01:38:00 -0000	[thread overview]
Message-ID: <4AE3AA51.9020602@vmware.com> (raw)
In-Reply-To: <200910231711.48441.pedro@codesourcery.com>

Pedro Alves wrote:
> On Friday 23 October 2009 16:44:06, Michael Snyder wrote:
>> Hey folks, we ran into a bunch of build problems because record.c
>> was being compiled in a lot of builds where it wasn't needed (or
>> tested).
>>
>> This change will make record.c be like gcore.c, in that it is only
>> built if the target config files explicitly call for it.
> 
> (You mean the host config file.)
> 
> No.  We had designed record_stratum so that it could be used
> transparently of whatever's the process_stratum target beneath, which
> allows precord to work against remote (gdbserver) and sim, e.g.,
> moxie precord support.

Hmmm, ok -- I must not have followed that discussion closely.

I don't think the fact that precord can work against whatever
target is beneath it has been widely advertised yet.  It certainly
hasn't been widely tested, eg. against remote.

I appreciate the desire, but is it ready for prime time?

Perhaps, as a compromise, we could link record.o against all
gdbs that currently link against gcore.o?  Which would include
most linuxen, many freebsd, and both i386 and sparc solaris?

> 
>> For this patch, I've only included record.c for i386-linux.
>> We can add amd64-linux in a separate patch if we decide it is
>> ready.

I should have gone on to say, and then add more hosts
as and when they are ready (assuming they also support gcore).


  parent reply	other threads:[~2009-10-25  1:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23 15:51 Michael Snyder
2009-10-23 16:11 ` Pedro Alves
2009-10-23 23:44   ` Michael Snyder
2009-10-25  1:38   ` Michael Snyder [this message]
2009-10-25  8:12     ` Pedro Alves
2009-10-25 18:41       ` Michael Snyder
2009-10-24  3:07 ` Hui Zhu

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=4AE3AA51.9020602@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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