Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: status on gdb-7.4 release...
Date: Thu, 22 Dec 2011 08:05:00 -0000	[thread overview]
Message-ID: <4EF2E2D6.8020503@rtems.org> (raw)
In-Reply-To: <20111222072526.GQ23376@adacore.com>

On 12/22/2011 08:25 AM, Joel Brobecker wrote:
>> gdb-7.3.91 installs $(includedir)/gdb/jit-reader.h
>> No idea what this is, why gdb does so and what it would be useful for.
>> To me it looks like a header without a corresponding library.
> Thanks.
>
> I don't know all the details, but this is the API that programs
> should use if they want to provide their own reader for JIT
> debug information. There is no need for a corresponding library
> as far as I know. See:
> http://www.sourceware.org/gdb/current/onlinedocs/gdb/JIT-Interface.html#JIT-Interface
>
OK, then ... wouldn't it be better to install this header into a 
versioned directory, say

$(includedir)/gdb-$(GDB_VERSION)
or
$(includedir)/gdb/$(GDB_VERSION)
?

Otherwise this file will conflict with other gdbs' versions of this file when having different versions of gdb installed in parallel[1] and should this file change in future versions of gdb.

Ralf

[1] I am building cross-gdbs to be installed in parallel to a system's native gdb and other cross-gdbs.



  reply	other threads:[~2011-12-22  7:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-22  7:09 Joel Brobecker
2011-12-22  7:25 ` Ralf Corsepius
2011-12-22  7:59   ` Joel Brobecker
2011-12-22  8:05     ` Ralf Corsepius [this message]
2011-12-22  8:41       ` Joel Brobecker
2011-12-22  9:33         ` Ralf Corsepius
2011-12-22 10:03 ` Jan Kratochvil
2011-12-22 10:13 ` Andreas Schwab
2011-12-22 10:21   ` Joel Brobecker
2011-12-22 10:35   ` Mark Kettenis
2011-12-22 17:07 ` Tom Tromey

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=4EF2E2D6.8020503@rtems.org \
    --to=ralf.corsepius@rtems.org \
    --cc=brobecker@adacore.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