Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: Framepointer


In the News (Sat 28 Nov 09)

  
  NationMaster - Encyclopedia: Framepointer   (Site not responding. Last check: 2007-10-27)
A framepointer or frame pointer is a pointer to the current stack frame.
It is generally used for debugging, but can also be used for stack management in general; the 68k processor series has instruction set support for framepointer access.
Maybe gcc's optimizer could be adapted in the (near) future to compare either speed or sizes of possibly generated code, with and without framepointer, if the compile is not a debug one.
www.nationmaster.com /encyclopedia/Framepointer   (446 words)

  
  Framepointer - Wikipedia, the free encyclopedia
A framepointer or frame pointer is a pointer to the current stack frame.
It is generally used for debugging, but can also be used for stack management in general; the 68k processor series has instruction set support for framepointer access.
Linux keeps track of the framepointer for each thread.
en.wikipedia.org /wiki/Framepointer   (93 words)

  
 [No title]
Add the code's size to the framepointer (r31) and you have the address of "/bin/sh".
We can't use nops or we would have to know the exact length of them (This would probably be the case since every instruction is 4 bytes, alignment is *really* important).
At the end of this file, you'll find an other shellcode (coded by nuuB) which doesn't use the framepointer but is double in size.
www.packetstormsecurity.org /papers/unix/m68koverflows   (685 words)

  
 LKML: David Zaffiro: Re: Compiling x86 with and without frame pointer
The slight overhead of leaf functions that do contain a dozen stackreferences is much smaller than the overhead of omitting framepointers in /all/ branch functions including those with dozens of stackreferences.
Maybe gcc's optimizer could be adapted in the (near) future to compare either speed or sizes of possibly generated code, with and without framepointer, if the compile is not a debug one.
But in the mean time, in most "userland" projects I've tested with, the -momit-leaf-frame-pointer resulted in almost te same codesize as compiles with framepointer, along with more or less the same speed as "-fomit-frame-pointer".
lkml.org /lkml/2002/11/25/15   (437 words)

  
 Eric Schrock's Weblog
The use of a framepointer is NOT mandated by the i386 UNIX ABI.
The ABI only _suggests_ that %ebp shall be used as a framepointer, giving function prologue/epilogue code samples that do it.
It twice mentions using %ebp as framepointer is optional, but explicitly states it must be preserved for the caller.
blogs.sun.com /roller/page/eschrock?entry=debugging_on_amd64_part_one   (1332 words)

  
 [No title]
barrier: (i stack elements at: framePointer - 3).
i@(Interpreter pointer) loadVariable: n [ i stackPush: (i method heapAllocate = CurrentMemory TrueObject ifTrue: [i lexicalContext variables at: n] ifFalse: [i stack elements at: i framePointer + n]) ] inline export.
offset = 0 ifTrue: [framePointer: i framePointer] ifFalse: [
slate.tunes.org /repos/alpha/_darcs/current/src/mobius/vm/base/vm.slate   (1247 words)

  
 Symbols and Source-level Debugging
The framepointer must be set to match your compiler before an IEEE-695 file is loaded.
The most common place to do this is in NOICE.NOI.
For other processors or compilers, consult your compiler documentation, or examine the generated code to see which register is being used as a frame pointer.
www.noicedebugger.com /help/symbols.htm   (4113 words)

  
 [No title]
"The namespace in which expressions are evaluated." addSlot: #framePointer valued: 0.
frame: (d interpreter stack at: d framePointer - 1).
d@(Debugger traits) evaluate: expr [ d evaluate: expr at: (d interpreter stack at: d framePointer - 1) ].
slate.tunes.org /repos/alpha/src/lib/debugger.slate   (898 words)

  
 Re: [fpc-devel] Local procedures as procedural parameter
This parameter must be passed, and possibly be removed from the stack, in every call to, and return from, a local subroutine.
All the technical details are already specified, by the current handling of local calls to local subroutines.
The only remarkable difference are static/dynamic checks, where direct calls can be handled at compile time, as is, whereas indirect calls would require a distinction at runtime, based on the local/global kind of the actual callback procedure.
www.mail-archive.com /fpc-devel@lists.freepascal.org/msg01974.html   (735 words)

  
 Q: watchpoint on framepointer   (Site not responding. Last check: 2007-10-27)
I want to be able to see the execution path (function sequences) without manually setting breakpoints on each function.
In theory a facility to set a watchpoint on the framepointer however I dont think GDB is designed to set watchpoints on registers.
Is there some method to recursively trace the sequence of function calls without having to set breakpoints manually?
www.mail-archive.com /bug-gdb@gnu.org/msg00477.html   (60 words)

  
 Profiler.txt   (Site not responding. Last check: 2007-10-27)
REM REM If you have a way to correlate pcode addresses with source code lines REM (no such way is currently available), you can comment out the lines REM which refer to LineNumber, and uncomment the lines which refer to REM FramePointer.
The report will then be reporting pcode addresses, and REM you will no longer have to compile with debug.
You will still not be REM able to track execution within VITAL subroutines and functions, but REM you will be able to track execution of code within INCLUDEd files.
www.vestatech.com /docs/Vstbman2004/vstbmanhtml/Ex_Etc/profiler.htm   (372 words)

  
 Table of Contents
Repeats An error class which indicatest that a repeating token or subframew within the message exceeded the boundaries of the enclosing subframe or that excess bytes remained at the end of the sequence or repetitions
in FramePointer bit offset of end of frame
This page was generated with the help of DOC++.
www.openss7.org /ss7codecs/docxx   (103 words)

  
 [No title]   (Site not responding. Last check: 2007-10-27)
This is the offset from the base of // the thread structure to the pointer to the kernel stack frame // for the currently active usermode callback.
// USHORT ThCallbackStack; // offset in thread data // // these values are offsets into that frame: // USHORT NextCallback; // saved pointer to next callback frame USHORT FramePointer; // saved frame pointer // // Address of the kernel callout routine.
// USHORT ThCallbackStack; // offset in thread data // // these values are offsets into that frame: // USHORT NextCallback; // saved pointer to next callback frame USHORT FramePointer; // saved frame pointer // // pad to a quad boundary // USHORT PaeEnabled:1; // // Address of the kernel callout routine.
www.cs.bgu.ac.il /~pcprogs/install/Microsoft_SDK/Include/WDbgExts.h   (1640 words)

  
 Re: HP-PA ABI issues - framepointer handling   (Site not responding. Last check: 2007-10-27)
To: dewar at gnat dot com, dje at watson dot ibm dot com
Subject: Re: HP-PA ABI issues - framepointer handling
From: dewar at gnat dot com (Robert Dewar)
gcc.gnu.org /ml/gcc/2000-10/msg00546.html   (260 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.