Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org, Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Subject: Re: [PATCH] Skip VDSO when reading SO list
Date: Fri, 20 Sep 2013 15:27:00 -0000	[thread overview]
Message-ID: <20130920152708.GA854@host2.jankratochvil.net> (raw)
In-Reply-To: <20130920131549.GA18629@host2.jankratochvil.net>

On Fri, 20 Sep 2013 15:15:49 +0200, Jan Kratochvil wrote:
> On Mon, 19 Aug 2013 16:44:13 +0200, Andreas Arnez wrote:
[...]
> > @@ -1349,10 +1350,22 @@ svr4_read_so_list (CORE_ADDR lm, CORE_AD
> >  	{
> >  	  struct svr4_info *info = get_svr4_info ();
> >  
> > +	  first = new;
> >  	  info->main_lm_addr = new->lm_info->lm_addr;
> >  	  do_cleanups (old_chain);
> >  	  continue;
> >  	}
> > +
> > +      /* The l_name of a VDSO sometimes lies in read-only memory that
>                             vDSO
> > +	 is excluded from a core dump.  In order to avoid the "can't
> > +	 read pathname" warning, we try to identify the VDSO.  One
>                                                         vDSO
> > +	 criteria is that the l_name address matches that of the main
> > +	 executable.  */
> > +      if (first && new->lm_info->l_name == first->lm_info->l_name)
> 
> Here should be also '&& ignore_first'.

I see now it is not needed.  FIRST would stay NULL in such case.

According to the GDB Coding standards s/first/first != NULL/ because FIRST is
a pointer.


Thanks,
Jan


  reply	other threads:[~2013-09-20 15:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19 14:44 Andreas Arnez
2013-08-19 18:30 ` Jan Kratochvil
2013-08-19 20:42   ` Joel Brobecker
2013-08-19 20:47     ` Jan Kratochvil
2013-08-19 21:13       ` Joel Brobecker
2013-08-20 11:44   ` Andreas Arnez
2013-08-20 13:47   ` Jan Kratochvil
2013-09-20 13:15 ` Jan Kratochvil
2013-09-20 15:27   ` Jan Kratochvil [this message]
2013-09-20 17:00   ` Andreas Arnez
2013-09-20 18:14     ` 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=20130920152708.GA854@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=krebbel@linux.vnet.ibm.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