Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: [rfc/rfa] Revsions to gdbint.texinfo
Date: Fri, 15 Jun 2001 00:14:00 -0000	[thread overview]
Message-ID: <3B29B5DE.30405@cygnus.com> (raw)

Hello,

The attatached patch tries to address the most glaring errors in the GDB 
internals document.  More work is always needed.

Structuring hints are welcome.

It includes a section titled ``Memory Management'' and that, in turn 
mentions alloca().

	Andrew
From brobecker@act-europe.fr Fri Jun 15 00:37:00 2001
From: Joel Brobecker <brobecker@act-europe.fr>
To: gdb-patches@sources.redhat.com
Subject: [RFA] Add 2 persons in MAINTAINERS
Date: Fri, 15 Jun 2001 00:37:00 -0000
Message-id: <20010615093709.B10775@act-europe.fr>
X-SW-Source: 2001-06/msg00286.html
Content-length: 349

Hi,

  Paul Hilfinger and I now have Write After Approval priviledges.
I updated the MAINTAINERS file accordingly (a patch is attached).
Here is the ChangeLog.

2001-06-15  Joel Brobecker <brobecker@act-europe.fr>

        * MAINTAINERS: Add Paul Hilfinger and Joel Brobecker to the
        Write After Approval list.

Ok for me to commit?
-- 
Joel
From eirik@hackrat.com Fri Jun 15 01:00:00 2001
From: Eirik Fuller <eirik@hackrat.com>
To: gdb-patches@sourceware.cygnus.com
Subject: [patch] read_command_lines can return freed memory
Date: Fri, 15 Jun 2001 01:00:00 -0000
Message-id: <20010615080029.8484D40014@hackrat.com>
X-SW-Source: 2001-06/msg00287.html
Content-length: 1246

When sourcing a script file with improperly nested control statments,
gdb can store a pointer to freed memory in a cmd_list_element struct,
which can cause subsequent crashes.  One test case is to source this
script file twice:


define	fp
    set $frame = (long *) $arg0
    while $frame[0] > $frame
	printf "%08x: %08x %08x\n", $frame, $frame[0], $frame[1]
	if $frame[1]
	    if ((uchar **)$frame)[1][-5] == 0xe8
		x/i $frame[1] - 5
	    else
		if ((uchar **)$frame)[1][-2] == 0xff
		    x/i $frame[1] - 2
		else
		    x/i $frame[1]
#		end
	    end
	else
	    x/i $frame[2]
	end
	set $frame = (long *) $frame[0]
    end
end


Removing the # results in a script file which can be sourced with no
errors.  The patch included here prevents the crash.  Here's a
ChangeLog entry:

2001-06-15  Eirik Fuller  <eirik@hackrat.com>

	* cli/cli-script.c (read_command_lines): Don't return freed
	memory.

Here's the patch:

--- gdb+dejagnu-20010615/gdb/cli/cli-script.c-	Tue Mar 13 14:29:14 2001
+++ gdb+dejagnu-20010615/gdb/cli/cli-script.c	Thu Jun 14 22:53:17 2001
@@ -995,7 +995,10 @@
 	  discard_cleanups (old_chain);
 	}
       else
-	do_cleanups (old_chain);
+	{
+	  do_cleanups (old_chain);
+	  head = NULL;
+	}
     }
 
   if (readline_end_hook)


             reply	other threads:[~2001-06-15  0:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-15  0:14 Andrew Cagney [this message]
2001-06-15  5:51 ` Eli Zaretskii
2001-06-15  8:15   ` Andrew Cagney
2001-06-15  8:33     ` Eli Zaretskii

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=3B29B5DE.30405@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.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