This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Breakpoint not hit because of function pointers or something similar
- From: Tom Tromey <tromey at redhat dot com>
- To: Anton MOUKHARSKI <anton dot moukharski at cea dot fr>
- Cc: gdb at sourceware dot org
- Date: Tue, 11 May 2010 12:59:18 -0600
- Subject: Re: Breakpoint not hit because of function pointers or something similar
- References: <4BE01FC1.8050309@cea.fr> <m3hbmfblsf.fsf@fleche.redhat.com> <4BE9232A.40904@cea.fr>
- Reply-to: Tom Tromey <tromey at redhat dot com>
>>>>> "Anton" == Anton MOUKHARSKI <anton.moukharski@cea.fr> writes:
Anton> Platform is Mandriva Linux release 2008.0 (Official) for i586 Kernel
Anton> 2.6.22.19-desktop-2mdv. Gdb version is GNU gdb 6.6-3.1mdv2008.0 (Mandriva
Anton> Linux release 2008.0).
6.6 is rather old. I would suggest upgrading first.
Anton> Again, the problem seems to be that the function in which I put
Anton> my breakpoint is called via a function-pointer (ip2 in the code
Anton> below); the function which is called below the call of
Anton> "process.execute()" is determined at execution time.
We will need a small, self-contained example showing the problem.
To my knowledge, gdb does not get confused if functions are called via
pointers. That works just fine when I am debugging gdb itself, for
instance.
Tom