Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Can we make gdbinit.in set the data-directory to @srcdir@?
Date: Fri, 02 Oct 2009 19:56:00 -0000	[thread overview]
Message-ID: <200910022056.30734.pedro@codesourcery.com> (raw)

While working on "catch syscall" issues, I found it weird
that a non-installed gdb ran from the build dir didn't pick
up the syscall names from the xml file found in its own sources.
I think it should, always, even when at some point distros start
including data in the default system data dir, which is meant for
the system gdb, not for the gdb one is hacking on.

Would anyone object to this?

-- 
Pedro Alves

2009-10-02  Pedro Alves  <pedro@codesourcery.com>

	* gdbinit.in: set data-directory to @srcdir@.

---
 gdb/gdbinit.in |    2 ++
 1 file changed, 2 insertions(+)

Index: src/gdb/gdbinit.in
===================================================================
--- src.orig/gdb/gdbinit.in	2009-10-01 15:15:16.000000000 +0100
+++ src/gdb/gdbinit.in	2009-10-02 20:45:52.000000000 +0100
@@ -16,6 +16,8 @@ dir @srcdir@
 dir .
 set prompt (top-gdb) 
 
+set data-directory @srcdir@
+
 define pdie
   if $argc == 1
     call dump_die ($arg0, 1)


             reply	other threads:[~2009-10-02 19:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 19:56 Pedro Alves [this message]
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
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=200910022056.30734.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    /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