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]

Re: pc_requires_run_before_use

From: Randolph Chung <randolph at tausq dot org>
To: John David Anglin <dave at hiauly1 dot hia dot nrc dot ca>
Cc: gdb at sources dot redhat dot com
Date: Tue, 23 Nov 2004 20:47:34 -0800
Subject: Re: pc_requires_run_before_use
References: <20041123212126.GR9148@tausq.org> <200411240344.iAO3iGm7008085@hiauly1.hia.nrc.ca>
Reply-to: Randolph Chung <randolph at tausq dot org>

> I haven't looked at this but I think this is typical of the plabel
> setup for lazy binding.  In GCC under linux, we need to call into
> the dynamic linker to force resolution of the function when doing
> function pointer comparisons.  This is the infamous __cffc routine.
> I think gdb will have similar issues when trying to set a break
> in a shared library.

no, i don't think that's it:

(gdb) b printf
Function "printf" not defined.
Make breakpoint pending on future shared library load? (y or [n]) n

gdb is pretty smart about this....

we used to have problems stepping into shared lib functions before they
have been resolved by the loader, but this has been fixed some time
back.

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

References:
- pc_requires_run_before_use
  - From: Randolph Chung
- Re: pc_requires_run_before_use
  - From: John David Anglin

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