This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Limited success with 3.0 branch on AIX
- To: Daniel Berlin <dan at www dot cgsoftware dot com>
- Subject: Re: Limited success with 3.0 branch on AIX
- From: David Edelsohn <dje at watson dot ibm dot com>
- Date: Tue, 01 May 2001 16:21:37 -0400
- cc: Nicholas Duffek <nsd at redhat dot com>, Kevin Buettner <kevinb at redhat dot com>, gdb at sources dot redhat dot com
The AIX stab-like choices are:
#define C_GSYM 0x80
#define C_LSYM 0x81
#define C_PSYM 0x82
#define C_RSYM 0x83
#define C_RPSYM 0x84
#define C_STSYM 0x85
#define C_TCSYM 0x86
#define C_BCOMM 0x87
#define C_ECOML 0x88
#define C_ECOMM 0x89
#define C_DECL 0x8c
#define C_ENTRY 0x8d
#define C_FUN 0x8e
#define C_BSTAT 0x8f
#define C_ESTAT 0x90
C_GSYM seemed to make the most sense to me. Would gdb looking in
N_GSYM cause a problem for any other ports? Should gdb look there only
for AIX?
Would N_GSYM symbol cause a conflict if a programmer really chose
to declare a global symbol named "gcc2_compiled."? Given the definition
of N_GSYM, it seems that this only would define a duplicate stabs entry
and not conflict with a real symbol of that same name because the stabs
value is ignored.
I would like to get a patch into GCC ASAP, but I want it to match
what GDB expects / can handle. So I would like to get a decision to use
G_NSYM or an alternate AIX stabs type, and get the simple changes into GCC
and GDB.
Thanks, David