From: kidoshisama <kidoshisama@gmail.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: Marty McGowan <mcgowan@alum.mit.edu>,
gdb@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: Building on Darwin
Date: Tue, 08 Nov 2011 15:15:00 -0000 [thread overview]
Message-ID: <CAB+SFK1dbFyPWfPKYbpUqum9hY7ND=ydqdJTEe3OM8eFz+V_Ow@mail.gmail.com> (raw)
In-Reply-To: <32D0F62F-19CA-486F-99F6-9159D23C418F@adacore.com>
I am having the same problem on my MBP, running Snow Leopard. I am no
longer getting the part about not being able to attach, but the
messages 'warning: can't find section '.const' in OSO file ...' and
'warning: can't find section '__DATA.__common' in OSO file...' are
still there, and any backtrace has no symbol info, i.e. '#0
0x00007fff8646d196 in ?? ()'.
If one looks in machoread.c, the failure seems to be in
macho_add_oso_symfile(); the code is looping through
oso->num_sections, and for each section it gets a name and then tries
to load a struct. Here is the code:
sectname = (char *)oso->symbols[i]->section->name;
sect = bfd_get_section_by_name (abfd, sectname);
if (sect == NULL)
{
warning (_("can't find section '%s' in OSO file %s"),
sectname, oso->name);
continue;
}
The section name is successfully read, but bfd_get_section_by_name()
returns NULL, apparently.
So this is as much as I know - can anyone please help me understand
the failure paths for this call (bfd_get_section_by_name)? Is there a
compilation flag being missed, or is it perhaps an incompatibility
with the gcc shipped wit XCode and the gdb I am building?
Any and all help would be greatly appreciated.
Thanks,
Keith
next prev parent reply other threads:[~2011-11-08 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 2:36 Marty McGowan
2011-06-21 4:20 ` Joel Brobecker
2011-06-21 7:37 ` Tristan Gingold
2011-11-08 15:15 ` kidoshisama [this message]
2011-11-09 7:51 ` Tristan Gingold
2011-12-23 5:46 ` alanandersen1
2011-12-23 10:32 ` 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='CAB+SFK1dbFyPWfPKYbpUqum9hY7ND=ydqdJTEe3OM8eFz+V_Ow@mail.gmail.com' \
--to=kidoshisama@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=gingold@adacore.com \
--cc=mcgowan@alum.mit.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).