Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
* [PATCH] Don't treat PC == 0 specially in inside_entry_func
@ 2004-01-10  0:22 Mark Kettenis
  2004-01-15 20:00 ` Mark Kettenis
  0 siblings, 1 reply; 2+ messages in thread
From: Mark Kettenis @ 2004-01-10  0:22 UTC (permalink / raw)
  To: gdb-patches

This stops us from treating a zero PC specially in inside_entry_func,
just like we did for inside_main_func.

If nobody objects, I'll check this in in a week or so.

Mark


Index: ChangeLog
from  Mark Kettenis  <kettenis@gnu.org>
 
	* blockframe.c (inside_entry_func): Don't treat a zero PC specially.

Index: blockframe.c
===================================================================
RCS file: /cvs/src/src/gdb/blockframe.c,v
retrieving revision 1.85
diff -u -p -r1.85 blockframe.c
--- blockframe.c 10 Jan 2004 00:09:58 -0000 1.85
+++ blockframe.c 10 Jan 2004 00:10:57 -0000
@@ -157,15 +157,11 @@ inside_main_func (CORE_ADDR pc)
 }
 
 /* Test whether PC is inside the range of addresses that corresponds
-   to the process entry point function.
-
-   A PC of zero is always considered to be the bottom of the stack.  */
+   to the process entry point function.  */
 
 int
 inside_entry_func (CORE_ADDR pc)
 {
-  if (pc == 0)
-    return 1;
   if (symfile_objfile == 0)
     return 0;
 


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-01-15 20:00 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-01-10  0:22 [PATCH] Don't treat PC == 0 specially in inside_entry_func Mark Kettenis
2004-01-15 20:00 ` Mark Kettenis

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox