From: Simon Marchi <simon.marchi@polymtl.ca>
To: Xavier Roirand <roirand@adacore.com>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com
Subject: Re: [RFA 2/5] Darwin: Handle unrelocated dyld.
Date: Wed, 22 Aug 2018 13:59:00 -0000 [thread overview]
Message-ID: <ee8425a17432881ee5be5b6594d46614@polymtl.ca> (raw)
In-Reply-To: <1534932677-9496-3-git-send-email-roirand@adacore.com>
On 2018-08-22 06:11, Xavier Roirand wrote:
> @@ -558,6 +600,56 @@ darwin_solib_create_inferior_hook (int from_tty)
> if (vmaddr != load_addr)
> objfile_rebase (symfile_objfile, load_addr - vmaddr);
> }
> +
> + /* Set solib notifier (to reload list of shared libraries). */
> + notifier = info->all_image.notifier;
> + info->notifier_set = 1;
> +
> + if (info->all_image.count == 0)
> + {
> + CORE_ADDR start;
> +
> + /* Dyld hasn't yet relocated itself, so the notifier address may
> be
> + incorrect (as it has to be relocated).
> + (Apparently dyld doesn't need to relocate itself on x86-64
> darwin,
> + but don't assume that).
> + Set an event breakpoint at the entry point. */
> + start = bfd_get_start_address (exec_bfd);
> + if (start == 0)
> + notifier = 0;
> + else
> + {
> + gdb_bfd_ref_ptr dyld_bfd (darwin_get_dyld_bfd ());
> + if (dyld_bfd != NULL)
> + {
> + CORE_ADDR dyld_bfd_start_address;
> + CORE_ADDR dyld_relocated_base_address;
> + CORE_ADDR pc;
> +
> + dyld_bfd_start_address = bfd_get_start_address
> (dyld_bfd.get());
> +
> + /* We find the dynamic linker's base address by
> examining
> + the current pc (which should point at the entry point
> + for the dynamic linker) and subtracting the offset of
> + the entry point. */
> +
> + pc = regcache_read_pc (get_current_regcache ());
> + dyld_relocated_base_address = pc -
> dyld_bfd_start_address;
> +
> + /* We get the proper notifier relocated address by
> + adding the dyld relocated base address to the current
> + notifier offset value. */
> +
> + notifier += dyld_relocated_base_address;
> + info->notifier_set = 0;
> + }
> + }
> + }
> +
> + /* Add the breakpoint which is hit by dyld when the list of solib is
> + modified. */
> + if (notifier != 0)
> + create_solib_event_breakpoint (target_gdbarch (), notifier);
> }
Also, if the process of finding the notifier address fails at any point,
could we display a warning?
Simon
next prev parent reply other threads:[~2018-08-22 13:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 10:11 [RFA 0/5] Fix some bugs on macOS Xavier Roirand
2018-08-22 10:11 ` [RFA 1/5] Darwin: fix bad loop incrementation Xavier Roirand
2018-08-22 13:14 ` Simon Marchi
2018-08-23 15:21 ` Simon Marchi
2018-08-22 10:11 ` [RFA 3/5] Darwin: set startup-with-shell to off on Sierra and later Xavier Roirand
2018-08-22 14:20 ` Simon Marchi
2018-08-22 14:37 ` Pedro Alves
2018-09-03 13:23 ` Xavier Roirand
2018-09-17 19:31 ` Tom Tromey
2018-08-22 10:11 ` [RFA 4/5] Darwin: fix thread ptid started by fork_inferior Xavier Roirand
2018-08-22 14:30 ` Simon Marchi
2018-08-22 16:10 ` Pedro Alves
2018-08-22 18:14 ` Simon Marchi
2018-08-22 10:11 ` [RFA 5/5] Darwin: fix SIGTRAP when debugging Xavier Roirand
2018-08-22 14:34 ` Simon Marchi
2018-08-22 10:11 ` [RFA 2/5] Darwin: Handle unrelocated dyld Xavier Roirand
2018-08-22 13:55 ` Simon Marchi
2018-09-18 21:22 ` Tom Tromey
2018-09-19 13:41 ` Joel Brobecker
2018-09-19 14:16 ` Simon Marchi
2018-09-19 14:28 ` Joel Brobecker
2018-09-19 14:36 ` Tom Tromey
2018-09-19 14:44 ` Simon Marchi
2018-09-19 15:32 ` Joel Brobecker
2018-09-19 19:15 ` Tom Tromey
2018-09-19 19:50 ` Simon Marchi
2018-09-28 13:31 ` Xavier Roirand
2018-09-28 17:22 ` Tom Tromey
2018-08-22 13:59 ` Simon Marchi [this message]
2018-09-18 21:23 ` Tom Tromey
2018-09-17 20:57 ` [RFA 0/5] Fix some bugs on macOS Tom Tromey
2018-09-17 21:25 ` Joel Brobecker
2018-09-17 23:03 ` 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=ee8425a17432881ee5be5b6594d46614@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=roirand@adacore.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