public inbox for frysk-cvs@sourceware.org
help / color / mirror / Atom feed
From: swagiaal@sourceware.org
To: frysk-cvs@sourceware.org
Subject: frysk-core/frysk debuginfo/ChangeLog debuginfo ...
Date: Fri, 22 Jun 2007 15:07:00 -0000	[thread overview]
Message-ID: <20070622150723.9949.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/frysk
Module name:	frysk-core
Changes by:	swagiaal@sourceware.org	2007-06-22 15:07:23

Modified files:
	frysk/debuginfo: ChangeLog DebugInfoEvaluator.java 
	frysk/rt       : ChangeLog Scope.java Variable.java 

Log message:
	Index: frysk-core/frysk/rt/ChangeLog
	2007-06-22  Sami Wagiaalla  <swagiaal@redhat.com>
	
	* Variable.java: Added constructor.
	* Scope.java: Replaced variable information arrays with a
	LinkedList of Variable Objects.
	(setVariables): Removed.
	(getVariableDies): Removed.
	(setVariableDies): Removed.
	(getTypeDies): Removed.
	(setTypeDies): Removed.
	
	Index: frysk-core/frysk/debuginfo/ChangeLog
	2007-06-22  Sami Wagiaalla  <swagiaal@redhat.com>
	
	* DebugInfoEvaluator.java: Re-enabled checking of cached Frame
	debug info.
	Replaced use of arrays from Subprogram with LinkedLists.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/debuginfo/ChangeLog.diff?cvsroot=frysk&r1=1.16&r2=1.17
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/debuginfo/DebugInfoEvaluator.java.diff?cvsroot=frysk&r1=1.13&r2=1.14
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/rt/ChangeLog.diff?cvsroot=frysk&r1=1.292&r2=1.293
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/rt/Scope.java.diff?cvsroot=frysk&r1=1.5&r2=1.6
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/rt/Variable.java.diff?cvsroot=frysk&r1=1.1&r2=1.2


             reply	other threads:[~2007-06-22 15:07 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22 15:07 swagiaal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-19 18:24 cagney
2007-10-18  2:45 cagney
2007-10-17 22:10 cagney
2007-10-14 16:49 cagney
2007-10-14 15:23 cagney
2007-10-12 21:53 cagney
2007-10-12 15:35 cagney
2007-10-10  3:07 cagney
2007-10-04 13:36 swagiaal
2007-10-03 20:25 cagney
2007-10-03 18:19 cagney
2007-10-03  2:26 cagney
2007-09-18 16:08 swagiaal
2007-09-13 18:25 swagiaal
2007-09-10 18:08 swagiaal
2007-09-07  0:00 cagney
2007-09-06 20:48 cagney
2007-09-06 14:26 cagney
2007-09-06  4:31 cagney
2007-09-06  3:19 cagney
2007-09-05 17:30 cagney
2007-09-05 15:09 cagney
2007-09-04 14:04 cagney
2007-08-31 22:47 cagney
2007-08-31 21:03 swagiaal
2007-08-31 19:33 cagney
2007-08-31 13:26 cagney
2007-08-31  2:25 cagney
2007-08-31  2:10 cagney
2007-08-31  1:57 cagney
2007-08-29 21:53 cagney
2007-08-29 20:31 swagiaal
2007-08-29 19:24 cagney
2007-08-29 18:45 swagiaal
2007-08-27 22:49 cagney
2007-08-24 15:28 cagney
2007-08-24 13:52 scox
2007-08-23 19:34 cagney
2007-08-22 13:34 cagney
2007-08-22  1:55 cagney
2007-08-21 20:22 scox
2007-08-21 19:56 swagiaal
2007-08-21  0:07 cagney
2007-08-20 16:12 cagney
2007-08-13 23:42 cagney
2007-08-10 18:02 scox
2007-08-10 15:38 swagiaal
2007-08-02 19:00 scox
2007-08-01 18:24 swagiaal
2007-07-31 21:39 swagiaal
2007-07-27 16:06 swagiaal
2007-07-09 16:01 scox
2007-07-09 14:51 cagney
2007-06-12 11:33 swagiaal
2007-05-29 19:59 swagiaal

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=20070622150723.9949.qmail@sourceware.org \
    --to=swagiaal@sourceware.org \
    --cc=frysk-cvs@sourceware.org \
    --cc=frysk@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).