Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: william@nscs.fast.net, kevinb@redhat.com
Cc: ac131313@ges.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: ChangeLog entry, re: gdb-5.2 and SCO OpenServer 5.0.5
Date: Fri, 16 Aug 2002 15:50:00 -0000	[thread overview]
Message-ID: <1020816225000.ZM32197@localhost.localdomain> (raw)
In-Reply-To: william@nscs.fast.net "Re: ChangeLog entry, re: gdb-5.2 and SCO OpenServer 5.0.5" (Aug 16,  6:18pm)

On Aug 16,  6:18pm, william@nscs.fast.net wrote:

> How is this:
> 
> 2002-08-16  William Bader  <william@nscs.fast.net>
> 
> 	* gdb/i386-tdep.c: Dynamically allocate buf;
> 	TARGET_PTR_BIT is not a constant.
> 
> --- gdb-5.2/gdb/i386-tdep.c-	Tue Feb 19 13:42:27 2002
> +++ gdb-5.2/gdb/i386-tdep.c	Fri Aug 16 18:13:00 2002
> @@ -858,7 +858,7 @@
>  int
>  get_longjmp_target (CORE_ADDR *pc)
>  {
> -  char buf[TARGET_PTR_BIT / TARGET_CHAR_BIT];
> +  char *buf = alloca (TARGET_PTR_BIT / TARGET_CHAR_BIT);
>    CORE_ADDR sp, jb_addr;
>  
>    sp = read_register (SP_REGNUM);

The patch looks good.  If it were me doing the ChangeLog entry,
I'd probably do it something like this:

	* i386-tdep.c (get_longjmp_target): Dynamically allocate ``buf''
	since TARGET_PTR_BIT is not a constant.

Or perhaps just:

	* i386-tdep.c (get_longjmp_target): Dynamically allocate ``buf''.

I just took a look at the current development sources and it looks to
me like this patch won't apply cleanly.  FWIW, the current development
sources don't use TARGET_PTR_BIT anymore (in the ``buf'' declaration)
so we're probably okay.

Kevin


  reply	other threads:[~2002-08-16 22:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-16 14:50 William Bader
2002-08-16 15:08 ` Kevin Buettner
2002-08-16 15:19   ` william
2002-08-16 15:50     ` Kevin Buettner [this message]
2002-08-16 17:08     ` Kevin Buettner

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=1020816225000.ZM32197@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=ac131313@ges.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=william@nscs.fast.net \
    /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