From: Tristan Gingold <gingold@ACT-Europe.FR>
To: gdb-patches@sourceware.org
Subject: [RFC] Darwin: add OSO as separate debug files
Date: Tue, 05 Jan 2010 11:32:00 -0000 [thread overview]
Message-ID: <20100105113232.GA11052@chinon.act-europe.fr> (raw)
Hi,
in order to correctly handle Darwin OSO files, they are now added as
separate debug objfile.
This is the Darwin specific use of the previous patch.
Tristan.
2009-12-23 Tristan Gingold <gingold@adacore.com>
* machoread.c (macho_add_oso_symfile): Add symfile_flags parameter.
Call xstrdup for abfd->filename. Pass symfile_flags and objfile flags
to symbol_file_add_from_bfd. Add OSO as separate objfile.
(macho_oso_symfile): Add symfile_flags parameter. Pass it to
macho_add_oso_symfile.
(macho_symfile_read): Pass symfile_flags to macho_oso_symfile.
---
gdb/machoread.c | 24 ++++++++++++++++++------
1 files changed, 18 insertions(+), 6 deletions(-)
diff --git a/gdb/machoread.c b/gdb/machoread.c
index 81f60ec..534fc94 100644
--- a/gdb/machoread.c
+++ b/gdb/machoread.c
@@ -292,8 +292,10 @@ oso_el_compare_name (const void *vl, const void *vr)
/* Add an oso file as a symbol file. */
static void
-macho_add_oso_symfile (oso_el *oso, bfd *abfd, struct objfile *main_objfile)
+macho_add_oso_symfile (oso_el *oso, bfd *abfd,
+ struct objfile *main_objfile, int symfile_flags)
{
+ struct objfile *objfile;
struct section_addr_info *addrs;
int len;
int i;
@@ -363,13 +365,22 @@ macho_add_oso_symfile (oso_el *oso, bfd *abfd, struct objfile *main_objfile)
addrs->other[j].name);
}
- symbol_file_add_from_bfd (abfd, 0, addrs, 0);
+ /* Make sure that the filename was malloc'ed. The current filename comes
+ either from an OSO symbol name or from an archive name. Memory for both
+ is not managed by gdb. */
+ abfd->filename = xstrdup (abfd->filename);
+
+ objfile = symbol_file_add_from_bfd
+ (abfd, symfile_flags, addrs,
+ main_objfile->flags & (OBJF_REORDERED | OBJF_SHARED
+ | OBJF_READNOW | OBJF_USERLOADED));
+ add_separate_debug_objfile (objfile, main_objfile);
}
/* Read symbols from the vector of oso files. */
static void
-macho_oso_symfile (struct objfile *main_objfile)
+macho_oso_symfile (struct objfile *main_objfile, int symfile_flags)
{
int ix;
VEC (oso_el) *vec;
@@ -453,7 +464,8 @@ macho_oso_symfile (struct objfile *main_objfile)
&& !memcmp (member_name, oso2->name + pfx_len + 1,
member_len))
{
- macho_add_oso_symfile (oso2, member_bfd, main_objfile);
+ macho_add_oso_symfile (oso2, member_bfd,
+ main_objfile, symfile_flags);
oso2->name = NULL;
break;
}
@@ -486,7 +498,7 @@ macho_oso_symfile (struct objfile *main_objfile)
warning (_("`%s': can't open to read symbols: %s."), oso->name,
bfd_errmsg (bfd_get_error ()));
else
- macho_add_oso_symfile (oso, abfd, main_objfile);
+ macho_add_oso_symfile (oso, abfd, main_objfile, symfile_flags);
ix++;
}
@@ -670,7 +682,7 @@ macho_symfile_read (struct objfile *objfile, int symfile_flags)
/* Then the oso. */
if (oso_vector != NULL)
- macho_oso_symfile (objfile);
+ macho_oso_symfile (objfile, symfile_flags);
}
static void
--
1.6.5.rc2
next reply other threads:[~2010-01-05 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 11:32 Tristan Gingold [this message]
2010-01-06 19:19 ` Tom Tromey
2010-01-07 9:05 ` Tristan Gingold
2010-01-14 12:48 ` Tristan Gingold
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=20100105113232.GA11052@chinon.act-europe.fr \
--to=gingold@act-europe.fr \
--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