From: "Dave.Tian" <xhengdf@gmail.com>
To: gdb-patches@sourceware.org
Cc: Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: [PATCH] bug fix for gdb 16039
Date: Wed, 16 Oct 2013 06:44:00 -0000 [thread overview]
Message-ID: <CAKjgB1OyrUtz9xqcqDSxEe72kDGEWBKy9LxZEkXDDd7RbX7y=A@mail.gmail.com> (raw)
In-Reply-To: <m3bo2pj3ha.fsf@redhat.com>
1 Description: Gdb bug 16039 created by me
Title: Gdb next" command stop working when shared library unloaded.
Root Cause: There is "libc++" static linked into the shared library,
and since gdb insert internal breakpoints on std::terminate/longjump/...
so after dlclose, the memory address is
invalid,remove_breakpoints/insert_breakpoints
failed with EIO error.
Fix: Disable the internal breakpoints when dlclose hit.
2 ChangeLog:
2013-10-16 Tian Ye <xhengdf@gmail.com>
PR gdb/16039
* breakpoint.c (is_removable_in_unloaded_shlib): New function.
(set_longjmp_breakpoint): Check if breakpoint's location
address is not in an unloaded shared library
(disable_breakpoints_in_unloaded_shlib): Disable the
internal breakpoints in the hook function of shared
library unload.
3 Patch Diffs:
--- breakpoint.c.bak 2013-10-12 01:15:09.044081000 -0700
+++ breakpoint.c 2013-10-15 23:10:50.241167000 -0700
@@ -1118,6 +1118,23 @@ is_tracepoint (const struct breakpoint *
return is_tracepoint_type (b->type);
}
+/* Return 1 if B is an internal memory breakpoint that
+ * can be removed when shlib is unloaded, or 0 otherwise. */
+
+static int
+is_removable_membreak_in_unloaded_shlib (const struct breakpoint *b)
+{
+ return (b->type == bp_longjmp
+ || b->type == bp_longjmp_resume
+ || b->type == bp_longjmp_call_dummy
+ || b->type == bp_exception
+ || b->type == bp_exception_resume
+ || b->type == bp_std_terminate
+ || b->type == bp_longjmp_master
+ || b->type == bp_std_terminate_master
+ || b->type == bp_exception_master);
+}
+
/* A helper function that validates that COMMANDS are valid for a
breakpoint. This function will throw an exception if a problem is
found. */
@@ -7147,8 +7164,8 @@ set_longjmp_breakpoint (struct thread_in
clones of those and enable them for the requested thread. */
ALL_BREAKPOINTS_SAFE (b, b_tmp)
if (b->pspace == current_program_space
- && (b->type == bp_longjmp_master
- || b->type == bp_exception_master))
+ && ((b->type == bp_longjmp_master
+ || b->type == bp_exception_master) && !b->loc->shlib_disabled))
{
enum bptype type = b->type == bp_longjmp_master ? bp_longjmp : bp_exception;
struct breakpoint *clone;
@@ -7463,7 +7480,8 @@ disable_breakpoints_in_unloaded_shlib (s
|| b->type == bp_hardware_breakpoint)
&& (loc->loc_type == bp_loc_hardware_breakpoint
|| loc->loc_type == bp_loc_software_breakpoint))
- || is_tracepoint (b))
+ || is_tracepoint (b)
+ || is_removable_in_unloaded_shlib (b))
&& solib_contains_address_p (solib, loc->address))
{
loc->shlib_disabled = 1;
thank you,
-YT
2013/10/15 Sergio Durigan Junior <sergiodj@redhat.com>:
> On Tuesday, October 15 2013, Dave Tian wrote:
>
>> 1 Description: Gdb bug 16039 created by me
>>
>> Title: Gdb next" command stop working when shared library unloaded.
>> Root Cause: There is "libc++" static linked into the shared library,
>> and since gdb insert internal breakpoints on std::terminate/longjump/...
>> so after dlclose, the memory address is
>> invalid,remove_breakpoints/insert_breakpoints
>> failed with EIO error.
>>
>> Fix: Disable the internal breakpoints when dlclose hit.
>
> Almost there, Dave! Thanks :-).
>
>> 2 ChangeLog:
>>
>> 2013-10-16 Tian Ye <xhengdf@gmail.com>
>>
>> PR gdb/16039
>> * breakpoint.c (is_removable_in_unloaded_shlib): New.
> ^^^^
>
> Write "New function" instead.
>
>> (set_longjmp_breakpoint): Check if breakpoint's location
>> address is not in an unloaded shared library
>> (disable_breakpoints_in_unloaded_shlib): Disable the
>> internal breakpoints in the hook function of shared
>> library unload.
>>
>> 3 Patch Diffs:
>>
>> --- breakpoint.c.bak 2013-10-12 01:15:09.044081000 -0700
>> +++ breakpoint.c 2013-10-15 18:50:59.842116000 -0700
>> @@ -1118,6 +1118,17 @@ is_tracepoint (const struct breakpoint *
>> return is_tracepoint_type (b->type);
>> }
>>
>> +/* Breakpoints should be disable when shlib unload. */
>
> The comment should describe what the function does. Something like:
>
> /* Return 1 if B is an internal breakpoint that can be removed when a
> shared library is unloaded, or 0 otherwise. */
>
>> +
>> +static int
>> +is_removable_in_unloaded_shlib(const struct breakpoint *b)
> ^^^
>
> Space between function name and parenthesis.
>
>> +{
>> + return (b->type == bp_longjmp_master
>> + || b->type == bp_std_terminate_master
>> + || b->type == bp_exception_master
>> + || b->type == bp_exception);
>> +}
>
> Also, would you mind explaining how you came to the conclusion that only
> those types of internal breakpoints can be present in a shared library?
> I looked a little bit through the code and could not find any
> explanation about this assumption. I remember that I commented that
> maybe you should extend this function in order to identify the other
> kinds of internal breakpoints...
>
> It would be nice to hear what other maintainers think of Dave's
> approach, so that he doesn't waste his with this detail.
>
>> +
>> /* A helper function that validates that COMMANDS are valid for a
>> breakpoint. This function will throw an exception if a problem is
>> found. */
>> @@ -7147,8 +7158,8 @@ set_longjmp_breakpoint (struct thread_in
>> clones of those and enable them for the requested thread. */
>> ALL_BREAKPOINTS_SAFE (b, b_tmp)
>> if (b->pspace == current_program_space
>> - && (b->type == bp_longjmp_master
>> - || b->type == bp_exception_master))
>> + && ((b->type == bp_longjmp_master
>> + || b->type == bp_exception_master) && !b->loc->shlib_disabled))
>> {
>> enum bptype type = b->type == bp_longjmp_master ? bp_longjmp : bp_exception;
>> struct breakpoint *clone;
>> @@ -7463,7 +7474,8 @@ disable_breakpoints_in_unloaded_shlib (s
>> || b->type == bp_hardware_breakpoint)
>> && (loc->loc_type == bp_loc_hardware_breakpoint
>> || loc->loc_type == bp_loc_software_breakpoint))
>> - || is_tracepoint (b))
>> + || is_tracepoint (b)
>> + || is_removable_in_unloaded_shlib(b))
> ^^^
>
> Space between function name and parenthesis.
>
>> && solib_contains_address_p (solib, loc->address))
>> {
>> loc->shlib_disabled = 1;
>
> --
> Sergio
next prev parent reply other threads:[~2013-10-16 6:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 2:18 Dave.Tian
2013-10-16 3:31 ` Sergio Durigan Junior
2013-10-16 6:44 ` Dave.Tian [this message]
2013-10-17 20:25 ` Tom Tromey
2013-10-19 4:38 ` Sergio Durigan Junior
2013-10-21 4:29 ` Dave.Tian
2013-10-28 23:33 ` Sergio Durigan Junior
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='CAKjgB1OyrUtz9xqcqDSxEe72kDGEWBKy9LxZEkXDDd7RbX7y=A@mail.gmail.com' \
--to=xhengdf@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@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