Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix breakpoints in unloaded shared libraries
Date: Tue, 22 Dec 2009 19:45:00 -0000	[thread overview]
Message-ID: <20091222194521.GA22089@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3637y7sjb.fsf@fleche.redhat.com>

On Tue, 22 Dec 2009 19:49:44 +0100, Tom Tromey wrote:
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> 
> Jan> breakpoints after:
> Jan> 	warning: Temporarily disabling breakpoints for ...
> Jan> are currently not handled correctly and GDB does even crash (with
> Jan> -lmcheck).
> 
> Jan> 2009-10-25  Jan Kratochvil  <jan.kratochvil@redhat.com>
> Jan> gdb/
> Jan> 	* breakpoint.c (bpstat_stop_status): Check BL->SHLIB_DISABLED.
> Jan> 	(print_breakpoint_location): New comment.  Check LOC->SHLIB_DISABLED.
> Jan> 	Check LOC validity before printing it.  Use LOC instead of B->LOC.
> Jan> 	Swap the if conditionals order.
> 
> This is ok.  Thanks.

The original mail had also the second part:

# 2009-10-25  Jan Kratochvil  <jan.kratochvil@redhat.com>
# 
# gdb/testsuite/
#         * gdb.base/unload.c (main): Change the UNLOADSHR parameter to 1.
#         Replace the printf call of Y by provided "y-set-1" label.  New block
#         for the second shared library.
#         * gdb.base/unload.exp: Compile also the second library, call
#         gdb_load_shlibs also for it.  Use now gdb_breakpoint.
#         (single pending breakpoint info): Rename to ...
#         (pending breakpoint info before run): ... this extended test.
#         (libfile2, libname2, libsrcfile2, libsrc2)
#         (lib_sl2): New variables.
#         (exec_opts): Set also SHLIB_NAME2.
#         (pending breakpoint info on first run at shrfunc1)
#         (pending breakpoint info on second run at shrfunc1)
#         (pending breakpoint info on second run at shrfunc2)
#         (print y from libfile, print y from libfile2): New tests.
#         * gdb.base/unloadshr.c (shrfunc1): Change the returned value.
#         * gdb.base/unloadshr2.c: New.

Do I understand it correctly your approval is for the gdb/ part while the
gdb/testsuite/ part is still left pending for review some other day?


Thanks for the review,
Jan


  reply	other threads:[~2009-12-22 19:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-25 15:21 Jan Kratochvil
2009-12-22 18:49 ` Tom Tromey
2009-12-22 19:45   ` Jan Kratochvil [this message]
2009-12-22 19:47     ` Tom Tromey
2009-12-23 22:26       ` Jan Kratochvil

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=20091222194521.GA22089@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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