Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <pedro@codesourcery.com>,
	        Joel Brobecker <brobecker@adacore.com>
Subject: Re: Can we make gdbinit.in set the data-directory to @srcdir@?
Date: Tue, 06 Oct 2009 04:44:00 -0000	[thread overview]
Message-ID: <200910060144.08110.sergiodj@linux.vnet.ibm.com> (raw)
In-Reply-To: <200910051441.47781.pedro@codesourcery.com>

On Monday 05 October 2009, Pedro Alves wrote:
> On Sunday 04 October 2009 14:53:58, Pedro Alves wrote:
> > On Friday 02 October 2009 22:05:06, Joel wrote:
> > > > 2009-10-02  Pedro Alves  <pedro@codesourcery.com>
> > > >
> > > > 	* gdbinit.in: set data-directory to @srcdir@.
> 
> On second thought, this was a bad idea.  .gdbinit is for the
> top (maybe system) gdb, not for the just built, non-installed
> gdb.  Sorry for the confusion.  I'll revert.


Also, there's one more thing I'd like to point out.  The catch syscall 
testcase partially relies in the fact that GDB will not have the data-
directory automatically set on startup.  This is because, among other things, 
it has to test how GDB behaves when it doesn't have access to the XML files 
for the architecture (or even when those files don't exist at all), and this 
scenario is achieved when data-directory is empty.

Anyway, if we decide to make this parameter be automatically set upon GDB's 
initialization in the build dir, we have to make sure that this doesn't break 
the testcase (I didn't test this specific case yet, but IIRC it's likely that 
it will break).  If it does, we may need to unset it on some situations inside 
the testcase in order to make it work properly.

Just my two cents.  Regards,

-- 
Sérgio Durigan Júnior
Linux on Power Toolchain - Software Engineer
Linux Technology Center - LTC
IBM Brazil


  reply	other threads:[~2009-10-06  4:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 19:56 Pedro Alves
2009-10-02 21:05 ` Joel Brobecker
2009-10-04 13:55   ` Pedro Alves
2009-10-05 13:41     ` Pedro Alves
2009-10-06  4:44       ` Sérgio Durigan Júnior [this message]
2009-10-06  5:34         ` Doug Evans
2009-10-06  9:33           ` Pedro Alves
2009-10-06  8:48         ` Pedro Alves
2009-11-22 23:00           ` Make sure catch-syscall.exp doesn't pick up system/installed syscalls xml Pedro Alves

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=200910060144.08110.sergiodj@linux.vnet.ibm.com \
    --to=sergiodj@linux.vnet.ibm.com \
    --cc=brobecker@adacore.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