Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Steve Ellcey <sellcey@mips.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: Pedro Alves <palves@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Avoid producing broken non-native core files
Date: Tue, 29 Oct 2013 17:02:00 -0000	[thread overview]
Message-ID: <1383066110.2558.177.camel@ubuntu-sellcey> (raw)
In-Reply-To: <alpine.DEB.1.10.1310190205580.12843@tp.orcam.me.uk>

On Wed, 2013-10-23 at 23:03 +0100, Maciej W. Rozycki wrote:


> Index: gdb-fsf-trunk-quilt/gdb/linux-tdep.c
> ===================================================================
> --- gdb-fsf-trunk-quilt.orig/gdb/linux-tdep.c	2013-10-21 12:15:29.727655132 +0100
> +++ gdb-fsf-trunk-quilt/gdb/linux-tdep.c	2013-10-21 12:15:53.727656870 +0100
> @@ -1209,14 +1209,15 @@ linux_corefile_thread_callback (struct t
>  				       args->note_data, args->note_size,
>  				       args->stop_signal);
>  
> -      if (siginfo_data != NULL)
> -	{
> +      /* Don't return anything if we got no register information above,
> +         such a core file is useless.  */
> +      if (args->note_data != NULL)
> +	if (siginfo_data != NULL)
>  	  args->note_data = elfcore_write_note (args->obfd,
>  						args->note_data,
>  						args->note_size,
>  						"CORE", NT_SIGINFO,
>  						siginfo_data, siginfo_size);
> -	}
>  
>        do_cleanups (old_chain);
>      }

Maciej,  I believe this change is the cause of a build failure for me
when using an old GCC (4.1.2) to build gdb.  I get:

cc1: warnings being treated as errors
/scratch/gcc/nightly/src/binutils-gdb/gdb/linux-tdep.c: In function
'linux_corefile_thread_callback':
/scratch/gcc/nightly/src/binutils-gdb/gdb/linux-tdep.c:1196: warning:
'siginfo_size' may be used uninitialized in this function

I do not get this error when using a newer GCC (like 4.4.3 or above).  I
can work around it by setting siginfo_size to 0 when it is declared.  I
don't know if there is a minimum GCC version required for building gdb
but my build with GCC 4.1.2 used to work.  Do you think initializing
siginfo_size is reasonable to allow us to use older GCC's to build gdb?

Steve Ellcey
sellcey@mips.com



  parent reply	other threads:[~2013-10-29 17:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 14:21 Maciej W. Rozycki
2013-10-16 15:22 ` Pedro Alves
2013-10-16 20:09   ` Maciej W. Rozycki
2013-10-18 15:12     ` Pedro Alves
2013-10-23 22:03       ` Maciej W. Rozycki
2013-10-24 14:32         ` Pedro Alves
2013-10-29 17:02         ` Steve Ellcey [this message]
2013-10-29 17:20           ` Maciej W. Rozycki
2013-10-29 17:28             ` Steve Ellcey
2013-10-29 17:38           ` Tom Tromey

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=1383066110.2558.177.camel@ubuntu-sellcey \
    --to=sellcey@mips.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@codesourcery.com \
    --cc=palves@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