This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

pending/1749: comments on GDB PR #1445


>Number:         1749
>Category:       pending
>Synopsis:       comments on GDB PR #1445
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   unknown
>Arrival-Date:   Mon Aug 16 12:38:02 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
   Hello!
 
 I have discovered even worse problem -- specifying a full 32-bit enum 
 value like `*0x80000001*' makes GDB unhappy.
 It complains `Cannot access memory at address 0x0' when I am trying to 
 print the value of that enum type.
 
 $ cat a.c
 enum some_t
 {
   x = 0x80000001,
   y = 0x80000002,
   z = 0x80000003
 };
 
 int
 main (void)
 {
   return 0;
 }
 $ gcc -g a.c
 $ gdb a.out
 GNU gdb Red Hat Linux (*5.3post-0.20021129.18rh*)
 Copyright 2003 Free Software Foundation, Inc.
 GDB is free software, covered by the GNU General Public License, and you are
 welcome to change it and/or distribute copies of it under certain 
 conditions.
 Type "show copying" to see the conditions.
 There is absolutely no warranty for GDB.  Type "show warranty" for details.
 This GDB was configured as "*i386-redhat-linux-gnu*".
 (gdb) p/d x
 Cannot access memory at address 0x0
 (gdb) ptype enum some_t
 type = enum some_t {x, y = 0, z = 0}
 (gdb) quit
 $
 
 Thanks.
 Alex
 
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]