Strange address in the stack trace

[santoshp]

Hi All,While debugging a crash dump using GDB (7.2) on RHEL-5, one address
looks strange to me. i.e. valueChanges variable. The same variable getting
passed to frames but shows different addresses in different frames. #1
0x00002aaaab8a163a in MR_AnyVal (this=0x2aaab9000020, *o=@0x52*) at
repos/mr/anyvali.c:36#2 0x00002aaaabb0fa13 in
MR_MonitoringSystem::valueChanges2monValueChanges
(*valueChanges=@0x465a5700*) at repos/mr/MR_MonitoredValue.h:61#3
0x00002aaaabb1065b in MR_MonitoringSystem::processChangesStandard
(*valueChanges=@0x465a5700*) at repos/mr/MR_MonitoringSystem.c:280#4
0x00002aaaabbb026c in MR_Accessor::notify (this=, *valueChanges=@0x52*) at
repos/accessors/MR_Accessor.c:1573Can somebody please comment on this
whether this is from OS (because it's optimized build) or the behavior from
GDB?Thanks,Santosh



--
View this message in context: http://sourceware-org.1504.n7.nabble.com/Strange-address-in-the-stack-trace-tp212534.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.