This is the mail archive of the gdb@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]

displaying source after and before the program counter


Hello,

I have a C++ program that generates a core dump. I must activate
inlining because it's too slow. It crashes very rarely.

The program stack is:

#2  0x080597da in CBase<TRow>::operator()() const () at
/home/ace/src/gs/mpvi.h:451
#3  0x081e0c1f in CPhrase::update() (this=0x115245d8) at
/home/ace/src/gs/mpvi.h:527

The problem is that CPhrase::update() is a big function in a cpp file. I
would like to know the line where the call to mpvi.h:527 is made. I
can't see it because the function is inlining and it's an accessor, so,
it's called at least 50 times on this function.

The question is: Is it possible to know where in the function ::update()
the crash happened?

Vianney Lecroart
---
lead network programmer / nevrax.com
icq#: 6870415
homepage: http://ace.planet-d.net
www.geekcode.com: GCS/E d- s+++: a- C+++$UL++ P- L+++>+$ E+>- W++ N+ o?
K- w++$ O- M- V- PS- PE? Y PGP t 5? X+ R- tv++ b- DI D+ G e++ h-- r y?



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