Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Aleksandar Ristovski <aristovski@qnx.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Set bfd field in target_section
Date: Tue, 28 Jul 2009 16:37:00 -0000	[thread overview]
Message-ID: <4A6F1647.70907@qnx.com> (raw)
In-Reply-To: <200907281606.05571.pedro@codesourcery.com>

Pedro Alves wrote:
> On Tuesday 28 July 2009 15:45:25, Aleksandar Ristovski wrote:
>> Pedro Alves wrote:
>>> On Tuesday 28 July 2009 15:28:33, Aleksandar Ristovski wrote:
>>>> Hello,
>>>>
>>>> I believe this is related to Pedro's patch from 03-Jun-09. I 
>>>> didn't see where we set target_section.bfd field - maybe I 
>>>> am overlooking something, but in bfd-target, in function 
>>>> target_bfd_xclose we will call bfd_close 
>>>> (table->sections->bfd); bfd_close doesn't like NULL argument.
>>>>
>>>> Am I missing something, or is this (the patch) missing?
>>> Doesn't add_to_section_table set the bfd in each new
>>> target section?
>> Indeed it does. However, the problem is if we don't find any 
>> sections in a bfd, it will exit and will leave bfd field 0.
> 
> Right, but table->sections will be equal to table->sections_end,
> meaning the table is empty.  Your fix isn't correct, since you
> should never write to *sections_end, which is one-past-the-end
> of the sections in the table.  In the degenerate case of
> bfd_count_sections == 0 (not 0 ALLOC sections), xmalloc will
> still return something non-NULL, but, writing to this pointer
> invokes undefined behaviour.
> 
>> I get this situation at the moment because I broke my 
>> xfer_partial, but I think it could happen in general?
> 
> Testing finished succesfully, so I've applied the patch
> with this ChangeLog entry.  Let me know if something is still wrong.
> 
> 2009-07-28  Pedro Alves  <pedro@codesourcery.com>
> 
> 	* bfd-target.c (target_bfd_xclose): Only close the bfd if the
> 	section table is not empty.
> 	(target_bfd_reopen): If the section table ends up empty, close the
> 	bfd here.
> 

I think now you broke it in a different way. Now we can end 
up trying to read from a closed bfd.


And just wondering, why not simply:

Index: gdb/exec.c
===================================================================
RCS file: /cvs/src/src/gdb/exec.c,v
retrieving revision 1.90
diff -u -p -r1.90 exec.c
--- gdb/exec.c	2 Jul 2009 17:21:06 -0000	1.90
+++ gdb/exec.c	28 Jul 2009 14:58:16 -0000
@@ -381,6 +381,7 @@ add_to_section_table (bfd *abfd, struct
    struct target_section **table_pp = (struct 
target_section **) table_pp_char;
    flagword aflag;

+  (*table_pp)->bfd = abfd;
    /* Check the section flags, but do not discard 
zero-length sections, since
       some symbols may still be attached to this section. 
For instance, we
       encountered on sparc-solaris 2.10 a shared library 
with an empty .bss
@@ -390,7 +391,6 @@ add_to_section_table (bfd *abfd, struct
    if (!(aflag & SEC_ALLOC))
      return;

-  (*table_pp)->bfd = abfd;
    (*table_pp)->the_bfd_section = asect;
    (*table_pp)->addr = bfd_section_vma (abfd, asect);
    (*table_pp)->endaddr = (*table_pp)->addr + 
bfd_section_size (abfd, asect);



-- 
Aleksandar Ristovski
QNX Software Systems


  reply	other threads:[~2009-07-28 15:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28 14:46 Aleksandar Ristovski
2009-07-28 14:51 ` Pedro Alves
2009-07-28 14:59   ` Pedro Alves
2009-07-28 15:06   ` Aleksandar Ristovski
2009-07-28 16:22     ` Pedro Alves
2009-07-28 16:37       ` Aleksandar Ristovski [this message]
2009-07-28 16:37         ` Pedro Alves
2009-07-28 21:48           ` Aleksandar Ristovski
2009-08-08 16:54             ` Pedro Alves
2009-07-28 15:16   ` Pedro Alves
2009-07-28 15:57     ` Aleksandar Ristovski

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=4A6F1647.70907@qnx.com \
    --to=aristovski@qnx.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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