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]

Re: gdb/1170: gdb-5.3 just doesn't work on aix5.1


The following reply was made to PR gdb/1170; it has been noted by GNATS.

From: Michael Veksler <VEKSLER@il.ibm.com>
To: gdb-gnats@sources.redhat.com
Cc:  
Subject: Re: gdb/1170: gdb-5.3 just doesn't work on aix5.1
Date: Sun, 19 Sep 2004 08:40:07 +0300

 It seems that in some cases (all?) /bin/as does not guarantee to preserve
 order of stab strings. I have created a small C++ fragment that will
 cause gdb crash if a stabstring is moved:
       // g++ -g
       struct X { static const int firstInt = 0; };
       struct Y { static const int secondInt = 0; };
       int main() { }
 This generates the following stabstrings:
       X:Tt12=s1firstInt:/213=k-1:......
       Y:Tt21=s1secondInt:/213:....
 (It should be interpreted as: "{name}:/2{type-id}=k-1:".
 Note that '/2' is not part of type-id).
 
 If you move the "firstInt" stabstring after the first stabstring of
 'main', gdb will crash. If gcc did not generate a separate type-id for
 'static const', it would not end up crashing gdb.
 
 


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