Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: [PATCH] thread-db.c: Avoid segfault by making sure that ``reg'' is initialized
Date: Fri, 19 Nov 2004 01:05:00 -0000	[thread overview]
Message-ID: <20041118175849.6c0ca16c@saguaro> (raw)
In-Reply-To: <20041118144457.56939409@saguaro>

On Thu, 18 Nov 2004 14:44:57 -0700
Kevin Buettner <kevinb@redhat.com> wrote:

> I've just committed the patch below.  As indicated by the subject line, this
> patch prevents a segfault when thread_db_set_thread_reg() returns an
> uninitialized ``reg''.  (This was happening on Fedora Core 2 due to lack of
> xregset support.)
> 
> 	* thread-db.c (thread_db_set_thread_reg): Don't allow a successful
> 	return without first initializing ``reg''.

My apologies for sending this to the wrong list.  This is an RDA patch, and
as such, I intended to send it to the RDA list.

Kevin


      reply	other threads:[~2004-11-19  0:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-19  0:59 Kevin Buettner
2004-11-19  1:05 ` Kevin Buettner [this message]

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=20041118175849.6c0ca16c@saguaro \
    --to=kevinb@redhat.com \
    --cc=gdb@sources.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