Re: [PATCH] Don't treat PC == 0 specially in inside_entry_func

[Mark Kettenis <kettenis@chello.nl>]

   Date: Sat, 10 Jan 2004 01:22:02 +0100 (CET)
   From: Mark Kettenis <kettenis@chello.nl>

   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.

I forgot to update the copyright year, so below is what I actually
checked in.

Mark


Index: ChangeLog
from  Mark Kettenis  <kettenis@gnu.org>

	* blockframe.c: Update copyright year.
	(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 15 Jan 2004 19:49:00 -0000
@@ -2,8 +2,8 @@
    functions and pc values.
 
    Copyright 1986, 1987, 1988, 1989, 1990, 1991, 1992, 1993, 1994,
-   1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003 Free Software
-   Foundation, Inc.
+   1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004
+   Free Software Foundation, Inc.
 
    This file is part of GDB.
 
@@ -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;