🚀 go-pugleaf

Return-Path: <jta@nic.funet.fi>
From: Juha Takala <jta@nic.funet.fi>
To: rms@ai.mit.edu (Richard Stallman)
Date: 	Tue, 16 Oct 1990 13:52:05 +0200

In-reply-to: rms@AI.MIT.EDU's message of 14 Oct 90 20:31:00 GMT
Subject: Ideas

   From: rms@AI.MIT.EDU (Richard Stallman)
   Newsgroups: gnu.gdb.bug

   I was reading a manual for another debugger and found the following ideas:
   ....
   * Have a way to set a breakpoint at the exit from a named function.
   (This might not work on machines that use individual return
   instructions, unless you want to scan the function for such
   instructions.  But we could fix this by making GCC use only one common
   return point when -O is not used.)

Could this be made by patching the return addres in the stack?  Change
the addres to some internal debugger routine, put the breakpoint there,
and restore the stack etc.  This does not work if we can't find room for
the code where to "return", but when compiled with '-g' that code might be
one extra library function.

Well, this works only when we are inside the function already, so that
the address is on the stack...  But if we patch the entry into the
function to do the work (to set the breakpoint), that might work...  Hmmm.

--
Juha Takala  (jta@sah.vtt.fi)  tel.: +358-0-456 6415   fax: +358-0-435 67014
Technical Research Centre, Laboratory of Electrical and Automation Engineering 
Otakaari 7 B, 02150 Espoo, FINLAND