From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: gdb-patches@sources.redhat.com
Subject: PATCH: solib-svr4.c needs to know what DT_MIPS_RLD_MAP is
Date: Fri, 08 Jun 2001 14:07:00 -0000 [thread overview]
Message-ID: <20010608140711.A6248@nevyn.them.org> (raw)
A block in solib-svr4.c is #ifdef'd on DT_MIPS_RLD_MAP, which is defined in
"elf/mips.h". Including that file would probably help. We could
conditionally include this file based on target, but I just went by other
files in GDB which referenced it and included it always.
How's this patch?
2001-06-08 Daniel Jacobowitz <drow@mvista.com>
* solib-svr4.c: Include "elf/mips.h".
(elf_locate_base): Make DT_MIPS_RLD_MAP block unconditional.
--
Daniel Jacobowitz Debian GNU/Linux Developer
Monta Vista Software Debian Security Team
From tromey@redhat.com Fri Jun 08 14:09:00 2001
From: Tom Tromey <tromey@redhat.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: Per Bothner <per@bothner.com>, Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: obvious set_cu_language patch
Date: Fri, 08 Jun 2001 14:09:00 -0000
Message-id: <8766e6eke4.fsf@creche.redhat.com>
References: <m24rtrwkfd.fsf@kelso.bothner.com> <3B212FC8.6010801@cygnus.com> <m2pucevgf6.fsf@kelso.bothner.com> <87vgm6snjf.fsf@cgsoftware.com>
X-SW-Source: 2001-06/msg00179.html
Content-length: 1295
>>>>> "Daniel" == Daniel Berlin <dan@cgsoftware.com> writes:
Daniel> Could you please point me to where i can find out what java
Daniel> arrays *are*, so i can make a type structure for them (the new
Daniel> typesystem is a hierarchy of structs, rather than a single
Daniel> type struct. This means whatever java arrays *are*, can
Daniel> easily be represented and handled, with no fuss or muss).
Java arrays are structures. You can see the definition in
gcc/libjava/gcj/array.h. I've appended the relevant bits for your
perusal.
Most instantiations of JArray are actually created at runtime. Only
primitive arrays are created statically.
Tom
class __JArray : public java::lang::Object
{
protected:
// This is just a hack to work around a warning emitted by the C++
// compiler. We initialize `length' evilly, but it doesn't know
// that.
__JArray () : length (0)
{
}
public:
const jsize length;
friend jsize JvGetArrayLength (__JArray*);
};
template<class T>
class JArray : public __JArray
{
T data[0];
public:
friend T* elements<>(JArray<T>& x);
friend T* elements<>(JArray<T>* x);
// T* getData() { return data; }
// T& operator[](jint i) { return data[i]; }
};
next reply other threads:[~2001-06-08 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-08 14:07 Daniel Jacobowitz [this message]
2001-06-18 17:28 ` Kevin Buettner
2001-06-18 19:53 ` Daniel Jacobowitz
2001-06-19 8:40 ` Andrew Cagney
2001-06-25 17:48 ` Kevin Buettner
2001-07-02 12:38 ` Daniel Jacobowitz
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=20010608140711.A6248@nevyn.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=gdb-patches@sources.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