This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: displaying source after and before the program counter
- From: Eli Zaretskii <eliz at elta dot co dot il>
- To: "Vianney Lecroart" <lecroart at nevrax dot com>
- Cc: gdb at sources dot redhat dot com
- Date: 15 Dec 2003 16:15:50 +0200
- Subject: Re: displaying source after and before the program counter
- References: <000b01c3c2f9$35a1fe80$0901a8c0@vianneyl>
- Reply-to: Eli Zaretskii <eliz at elta dot co dot il>
> From: "Vianney Lecroart" <lecroart@nevrax.com>
> Date: Mon, 15 Dec 2003 11:50:09 +0100
>
> 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?
Without turning off the inlining, yes?
Well, one way to do that is to look at the machine code in frame #3
(by using the `disassemble' command), then compare that with the
assembly generated by the compiler for the source code in question.
For the latter, invoke GCC exactly as it is invoked to compile the cpp
file which includes mpvi.h, but with the -S switch instead of the -c
switch. (There are also switches that you can add to cause the
generated assembly to include source lines, which will make it easier
for you to associate the assembly with the source.)
HTH