From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v4 00/18] All-stop on top of non-stop
Date: Wed, 12 Aug 2015 19:05:00 -0000 [thread overview]
Message-ID: <55CB9907.9080506@redhat.com> (raw)
In-Reply-To: <20150812183208.GA24901@adacore.com>
On 08/12/2015 07:32 PM, Joel Brobecker wrote:
> This uncovered what I think is a latent bug in the "how-did-we-never-
> see-this-before" category.
Wow! Indeed. Many thanks for tracking this down and fixing it.
A couple minor comments below, but this looks good to me.
> Does this patch look OK to you?
> * gdb.base/dso2dso-impl.c, gdb.base/dso2dso-impl.h,
> gdb.base/dso2dso-pck.c, gdb.base/dso2dso-pck.h, gdb.base/dso2dso.c,
> gdb.base/dso2dso.exp: New files.
>
Nit: the "pck" and "impl"s here confuse me -- I guess they meant something
in the original test? Do they still have any meaning here? I'd suggest
renaming to dso2dso-dso1.c, dso2dso-dso2.c, and then
sub() -> sub1(), impl__initialize() -> sub2(). That way, it should
be clearer that a function in dso1 calls a function in dso2.
> diff --git a/gdb/amd64-tdep.c b/gdb/amd64-tdep.c
> index 5e63b5e..5b4a8f4 100644
> --- a/gdb/amd64-tdep.c
> +++ b/gdb/amd64-tdep.c
> @@ -1662,7 +1662,7 @@ amd64_displaced_step_fixup (struct gdbarch *gdbarch,
>
> regcache_cooked_read_unsigned (regs, AMD64_RSP_REGNUM, &rsp);
> retaddr = read_memory_unsigned_integer (rsp, retaddr_len, byte_order);
> - retaddr = (retaddr - insn_offset) & 0xffffffffUL;
> + retaddr = (retaddr - insn_offset) & 0xffffffffffffffffUL;
I think this should use the ULL suffix now.
> +
> +if { [gdb_compile_shlib $srcfile_libimpl $binfile_libimpl \
> + [list debug additional_flags=-fPIC]] != "" } {
> + untested "Could not compile $binfile_libimpl."
> + return -1
> +}
> +
> +if { [gdb_compile_shlib $srcfile_libpck $binfile_libpck \
> + [list debug additional_flags=-fPIC]] != "" } {
> + untested "Could not compile $binfile_libpck."
> + return -1
> +}
> +
> +if { [gdb_compile $srcdir/$subdir/$srcfile $binfile executable \
> + [list debug shlib=$binfile_libimpl shlib=$binfile_libpck]] != "" } {
> + return -1
> +}
> +
> +clean_restart $binfile
> +
I think a
gdb_load_shlibs $binfile_libimpl $binfile_libpck
is missing here.
> +if { ![runto_main] } {
> + return -1
> +}
> +
> +set bp_location [gdb_get_line_number "impl__initialize" $srcfile_libpck]
> +gdb_breakpoint ${srcfile_libpck}:${bp_location}
> +
> +gdb_continue_to_breakpoint "at call to impl__initialize" \
> + ".*impl__initialize ().*"
> +
> +gdb_test "next" \
> + ".*return 5;.*" \
> + "next over call to impl__initialize"
> -- 2.1.4
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-08-12 19:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 23:19 Pedro Alves
2015-05-21 23:19 ` [PATCH 08/18] Add comments to currently_stepping and target_resume Pedro Alves
2015-05-21 23:19 ` [PATCH 18/18] native Linux: enable always non-stop by default Pedro Alves
2015-05-21 23:19 ` [PATCH 12/18] Fix signal-while-stepping-over-bp-other-thread.exp on targets always in non-stop Pedro Alves
2015-05-21 23:19 ` [PATCH 06/18] Use keep_going in proceed and start_step_over too Pedro Alves
2015-05-21 23:19 ` [PATCH 01/18] Fix and test "checkpoint" in non-stop mode Pedro Alves
2015-05-21 23:19 ` [PATCH 04/18] Make thread_still_needs_step_over consider stepping_over_watchpoint too Pedro Alves
2015-05-21 23:19 ` [PATCH 14/18] Fix step-over-{trips-on-watchpoint|lands-on-breakpoint}.exp race Pedro Alves
2015-05-21 23:19 ` [PATCH 11/18] Implement all-stop on top of a target running non-stop mode Pedro Alves
2015-09-11 20:53 ` Jan Kratochvil
2015-09-14 14:24 ` Pedro Alves
2015-05-21 23:19 ` [PATCH 09/18] Factor out code to re-resume stepped thread Pedro Alves
2015-05-21 23:19 ` [PATCH 16/18] PPC64: Fix gdb.arch/ppc64-atomic-inst.exp with displaced stepping Pedro Alves
2015-05-21 23:19 ` [PATCH 03/18] remote.c/all-stop: Implement TARGET_WAITKIND_NO_RESUMED and TARGET_WNOHANG Pedro Alves
2015-05-21 23:19 ` [PATCH 02/18] Change adjust_pc_after_break's prototype Pedro Alves
2015-05-21 23:19 ` [PATCH 05/18] Embed the pending step-over chain in thread_info objects Pedro Alves
2015-05-21 23:25 ` [PATCH 07/18] Misc switch_back_to_stepped_thread cleanups Pedro Alves
2015-05-21 23:28 ` [PATCH 13/18] Fix interrupt-noterm.exp on targets always in non-stop Pedro Alves
2015-05-21 23:50 ` [PATCH 17/18] S/390: displaced stepping and PC-relative RIL-b/RIL-c instructions Pedro Alves
2015-05-21 23:56 ` [PATCH 10/18] Teach non-stop to do in-line step-overs (stop all, step, restart) Pedro Alves
2015-05-21 23:59 ` [PATCH 15/18] Disable displaced stepping if trying it fails Pedro Alves
2015-08-07 16:58 ` [PATCH v4 00/18] All-stop on top of non-stop Pedro Alves
2015-08-12 18:32 ` Joel Brobecker
2015-08-12 19:05 ` Pedro Alves [this message]
2015-08-12 20:26 ` Joel Brobecker
2015-08-12 20:31 ` Luis Machado
2015-08-12 20:50 ` Joel Brobecker
2015-08-12 21:07 ` Luis Machado
2015-08-13 16:04 ` Pedro Alves
2015-08-13 18:17 ` Joel Brobecker
2015-08-13 17:27 ` Pedro Alves
2015-08-13 18:29 ` Joel Brobecker
2015-08-12 19:39 ` Luis Machado
2015-08-12 19:51 ` Sergio Durigan Junior
2015-08-12 19:59 ` Joel Brobecker
2015-08-12 20:18 ` Luis Machado
2015-08-12 20:33 ` Joel Brobecker
2015-08-12 20:40 ` Luis Machado
2015-08-12 20:56 ` Joel Brobecker
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=55CB9907.9080506@redhat.com \
--to=palves@redhat.com \
--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