File: StackFrameInfo.java

package info (click to toggle)
spidermonkey 1.5rc6a-1
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 6,676 kB
  • ctags: 11,462
  • sloc: ansic: 82,178; cpp: 11,392; java: 859; perl: 722; makefile: 638; asm: 75; awk: 20; sh: 7
file content (98 lines) | stat: -rw-r--r-- 3,043 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
/* -*- Mode: C; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 2 -*-
 *
 * The contents of this file are subject to the Netscape Public
 * License Version 1.1 (the "License"); you may not use this file
 * except in compliance with the License. You may obtain a copy of
 * the License at http://www.mozilla.org/NPL/
 *
 * Software distributed under the License is distributed on an "AS
 * IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
 * implied. See the License for the specific language governing
 * rights and limitations under the License.
 *
 * The Original Code is mozilla.org code.
 *
 * The Initial Developer of the Original Code is Netscape
 * Communications Corporation.  Portions created by Netscape are
 * Copyright (C) 1998 Netscape Communications Corporation. All
 * Rights Reserved.
 *
 * Contributor(s): 
 */

package netscape.jsdebug;

/**
* This interface provides access to the execution stack of a thread.
* It has several subclasses to distinguish between different kinds of
* stack frames: these currently include activations of Java methods
* or JavaScript functions.
* It is possible that synchronize blocks and try blocks deserve their own
* stack frames - to allow for later extensions a debugger should skip over
* stack frames it doesn't understand.
* Note that this appears very Java-specific.  However, multiple threads and
* exceptions are relevant to JavaScript as well because of its
* interoperation with Java.
*
* @author  John Bandhauer
* @author  Nick Thompson
* @version 1.0
* @since   1.0
*/
public abstract class StackFrameInfo {
    ThreadStateBase threadState;
    StackFrameInfo caller;

    protected StackFrameInfo(ThreadStateBase threadState) {
        this.threadState = threadState;
    }

    /**
     * Return true if this stack frame is still valid.  Stack frames
     * may become invalid when the thread is resumed (this is more
     * conservative than invalidating the frame only when it actually
     * returns).
     */
    public boolean isValid() {
        return threadState.isValid();
    }

    /**
     * Get the stack frame where this one was built, or null for the
     * start of the stack.
     */
    public synchronized StackFrameInfo getCaller()
        throws InvalidInfoException {
        if (caller == null)
            caller = getCaller0();
        if (!isValid())
            throw new InvalidInfoException("invalid StackFrameInfo");
        return caller;
    }

    protected abstract StackFrameInfo getCaller0()
        throws InvalidInfoException;

    /**
     * Get the thread that this stack frame is a part of.
     */
    public Thread getThread() {
        return threadState.getThread();
    }

    /**
     * Get the 'enclosing' thread state
     */
    public ThreadStateBase getThreadState() {
        return threadState;
    }


    /**
     * Get the current program counter value.  Note that the
     * class JavaPC supports the getMethod() operation.
     */
    public abstract PC getPC()
        throws InvalidInfoException;
}