Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] [gdb/symtab] Fix htab_find_slot call in read_call_site_scope
Date: Sun, 3 Oct 2021 21:34:05 +0200	[thread overview]
Message-ID: <f34e5c49-9e86-c697-a635-078caca317f9@suse.de> (raw)
In-Reply-To: <113a7cab-f06b-32ad-caa1-b0c87e67335b@polymtl.ca>

[-- Attachment #1: Type: text/plain, Size: 2716 bytes --]

On 10/1/21 3:09 PM, Simon Marchi wrote:
> 
> 
> On 2021-10-01 08:33, Tom de Vries via Gdb-patches wrote:
>> From: Simon Marchi <simon.marchi@polymtl.ca>
>>
>> In read_call_site_scope we have:
>> ...
>>   call_site_local.pc = pc;
>>   slot = htab_find_slot (cu->call_site_htab, &call_site_local, INSERT);
>> ...
>>
>> The call passes a call_site pointer as element.  OTOH, the hashtab is created
>> using hash_f == core_addr_hash and eq_f == core_addr_eq, so the element
>> will be accessed through a CORE_ADDR pointer.
>>
>> This is not wrong (at least in C), given that pc is the first field in
>> call_site.
>>
>> Nevertheless, as in call_site_for_pc, make the htab_find_slot call match the
>> used hash_f and eq_f by using &pc instead:
>> ...
>>   slot = htab_find_slot (cu->call_site_htab, &pc, INSERT);
>> ...
>>
>> Tested on x86_64-linux.
>>
>> Co-Authored-By: Tom de Vries <tdevries@suse.de>
>> ---
>>  gdb/dwarf2/read.c | 5 ++---
>>  gdb/gdbtypes.h    | 4 +---
>>  2 files changed, 3 insertions(+), 6 deletions(-)
>>
>> diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c
>> index 00aa64dd0ab..23870c04e74 100644
>> --- a/gdb/dwarf2/read.c
>> +++ b/gdb/dwarf2/read.c
>> @@ -13341,7 +13341,7 @@ read_call_site_scope (struct die_info *die, struct dwarf2_cu *cu)
>>    struct gdbarch *gdbarch = objfile->arch ();
>>    CORE_ADDR pc, baseaddr;
>>    struct attribute *attr;
>> -  struct call_site *call_site, call_site_local;
>> +  struct call_site *call_site;
>>    void **slot;
>>    int nparams;
>>    struct die_info *child_die;
>> @@ -13369,8 +13369,7 @@ read_call_site_scope (struct die_info *die, struct dwarf2_cu *cu)
>>      cu->call_site_htab = htab_create_alloc_ex (16, core_addr_hash, core_addr_eq,
>>  					       NULL, &objfile->objfile_obstack,
>>  					       hashtab_obstack_allocate, NULL);
>> -  call_site_local.pc = pc;
>> -  slot = htab_find_slot (cu->call_site_htab, &call_site_local, INSERT);
>> +  slot = htab_find_slot (cu->call_site_htab, &pc, INSERT);
>>    if (*slot != NULL)
>>      {
>>        complaint (_("Duplicate PC %s for DW_TAG_call_site "
>> diff --git a/gdb/gdbtypes.h b/gdb/gdbtypes.h
>> index 2a641122aec..84b751e82e3 100644
>> --- a/gdb/gdbtypes.h
>> +++ b/gdb/gdbtypes.h
>> @@ -1783,9 +1783,7 @@ struct call_site_parameter
>>  
>>  struct call_site
>>    {
>> -    /* * Address of the first instruction after this call.  It must be
>> -       the first field as we overload core_addr_hash and core_addr_eq
>> -       for it.  */
> 
> Ah, I had not seen this comment.  So it was on purpose.  Still, I think
> that it makes it more confusing than anything.  The patch LGTM.

And, this follow-up commit reverts everything except the comment.

Any comments?

Thanks,
- Tom


[-- Attachment #2: 0001-gdb-symtab-Add-call_site_eq-and-call_site_hash.patch --]
[-- Type: text/x-patch, Size: 3944 bytes --]

[gdb/symtab] Add call_site_eq and call_site_hash

In commit b4c919f7525 "[gdb/symtab] Fix htab_find_slot call in
read_call_site_scope" , I removed the comment:
...
It must be the first field as we overload core_addr_hash and core_addr_eq for
it.
...
for field pc of struct call_site.

However, this was not tested, and when indeed moving field pc to the second
location, we run into a testsuite failure in gdb.trace/entry-values.exp.

This is caused by core_addr_eq (the eq_f function for the htab) being
called with a pointer to the pc field (as passed into htab_find_slot) and a
pointer to a hash table element.  Now that pc is no longer the first field,
the pointer to hash table element no longer points to the pc field.

This could be fixed by simply reinstating the comment, but we're trying to
get rid of this kind of tricks that make refactoring more difficult.

Instead, fix this by:
- reverting commit b4c919f7525, apart from the comment removal, such that
  we're passing a pointer to element to htab_find_slot
- updating the htab_find_slot call in compunit_symtab::find_call_site
  in a similar manner
- adding a call_site_eq and call_site_hash, and using these in the hash table
  instead of core_addr_eq and core_addr_hash.

Tested on x86_64-linux, both with and without a trigger patch that moves pc to
the second location in struct call_site.

---
 gdb/dwarf2/read.c |  7 ++++---
 gdb/gdbtypes.h    | 15 +++++++++++++++
 gdb/symtab.c      |  5 ++++-
 3 files changed, 23 insertions(+), 4 deletions(-)

diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c
index 2d4ca08b667..75d6853fd5b 100644
--- a/gdb/dwarf2/read.c
+++ b/gdb/dwarf2/read.c
@@ -13341,7 +13341,7 @@ read_call_site_scope (struct die_info *die, struct dwarf2_cu *cu)
   struct gdbarch *gdbarch = objfile->arch ();
   CORE_ADDR pc, baseaddr;
   struct attribute *attr;
-  struct call_site *call_site;
+  struct call_site *call_site, call_site_local;
   void **slot;
   int nparams;
   struct die_info *child_die;
@@ -13366,10 +13366,11 @@ read_call_site_scope (struct die_info *die, struct dwarf2_cu *cu)
   pc = gdbarch_adjust_dwarf2_addr (gdbarch, pc);
 
   if (cu->call_site_htab == NULL)
-    cu->call_site_htab = htab_create_alloc_ex (16, core_addr_hash, core_addr_eq,
+    cu->call_site_htab = htab_create_alloc_ex (16, call_site_hash, call_site_eq,
 					       NULL, &objfile->objfile_obstack,
 					       hashtab_obstack_allocate, NULL);
-  slot = htab_find_slot (cu->call_site_htab, &pc, INSERT);
+  call_site_local.pc = pc;
+  slot = htab_find_slot (cu->call_site_htab, &call_site_local, INSERT);
   if (*slot != NULL)
     {
       complaint (_("Duplicate PC %s for DW_TAG_call_site "
diff --git a/gdb/gdbtypes.h b/gdb/gdbtypes.h
index 6d09576208d..8021cb21ecc 100644
--- a/gdb/gdbtypes.h
+++ b/gdb/gdbtypes.h
@@ -1824,6 +1824,21 @@ struct call_site
     struct call_site_parameter parameter[1];
   };
 
+static inline int
+call_site_eq (const void *a_, const void *b_)
+{
+  const struct call_site *a = (const call_site *)a_;
+  const struct call_site *b = (const call_site *)b_;
+  return core_addr_eq (&a->pc, &b->pc);
+}
+
+static inline hashval_t
+call_site_hash (const void *a_)
+{
+  const struct call_site *a = (const call_site *)a_;
+  return core_addr_hash (&a->pc);
+}
+
 /* The type-specific info for TYPE_CODE_FIXED_POINT types.  */
 
 struct fixed_point_type_info
diff --git a/gdb/symtab.c b/gdb/symtab.c
index 6ec5d95401e..84193ddaae3 100644
--- a/gdb/symtab.c
+++ b/gdb/symtab.c
@@ -334,10 +334,13 @@ search_domain_name (enum search_domain e)
 call_site *
 compunit_symtab::find_call_site (CORE_ADDR pc) const
 {
+  struct call_site call_site_local;
   if (m_call_site_htab == nullptr)
     return nullptr;
 
-  void **slot = htab_find_slot (m_call_site_htab, &pc, NO_INSERT);
+  call_site_local.pc = pc;
+  void **slot
+    = htab_find_slot (m_call_site_htab, &call_site_local, NO_INSERT);
   if (slot == nullptr)
     return nullptr;
 

  reply	other threads:[~2021-10-03 19:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01 12:33 Tom de Vries via Gdb-patches
2021-10-01 12:33 ` [PATCH 2/4] [gdb/symtab] Remove COMPUNIT_CALL_SITE_HTAB Tom de Vries via Gdb-patches
2021-10-01 13:13   ` Simon Marchi via Gdb-patches
2021-10-01 12:33 ` [PATCH 3/4] [gdb/symtab] Add call_site::pc () Tom de Vries via Gdb-patches
2021-10-01 18:10   ` Simon Marchi
2021-10-04 16:45     ` Tom de Vries via Gdb-patches
2021-10-01 12:33 ` [PATCH 4/4] [gdb/symtab] Use unrelocated addresses in call_site Tom de Vries via Gdb-patches
2021-10-01 20:56   ` Simon Marchi via Gdb-patches
2021-10-04 16:47     ` Tom de Vries via Gdb-patches
2021-10-01 13:09 ` [PATCH 1/4] [gdb/symtab] Fix htab_find_slot call in read_call_site_scope Simon Marchi via Gdb-patches
2021-10-03 19:34   ` Tom de Vries via Gdb-patches [this message]
2021-10-04 12:05     ` Simon Marchi via Gdb-patches
2021-10-04 12:46       ` Tom de Vries via Gdb-patches
2021-10-04 15:41         ` Simon Marchi via Gdb-patches
2021-10-04 16:14           ` Tom de Vries via Gdb-patches
2021-10-04 16:34             ` Simon Marchi via Gdb-patches

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=f34e5c49-9e86-c697-a635-078caca317f9@suse.de \
    --to=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=tdevries@suse.de \
    /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