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: [patch/rfc] How to handle stepping into an unresolved plt entry?

From: Randolph Chung <randolph at tausq dot org>
To: Andrew Cagney <cagney at gnu dot org>
Cc: gdb at sources dot redhat dot com
Date: Mon, 24 May 2004 11:52:51 -0700
Subject: Re: [patch/rfc] How to handle stepping into an unresolved plt entry?
References: <20040521064435.GJ566@tausq.org> <40AE27AC.6090205@gnu.org> <20040521182138.GN566@tausq.org> <40B231BE.50609@gnu.org>
Reply-to: Randolph Chung <randolph at tausq dot org>

> Anyway, can the IN_SOLIB_RETURN_TRAMPOLINE be moved up as well (with an 
> additional ecs->stop_func_name != NULL check?

I don't think checking the stop_func_name is correct; some trampolines
can be named. For example on hpux the export stubs are named. On both
hppa-linux and hpux there is a $$dyncall stub which is named.

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

References:
- [patch/rfc] How to handle stepping into an unresolved plt entry?
  - From: Randolph Chung
- Re: [patch/rfc] How to handle stepping into an unresolved plt entry?
  - From: Andrew Cagney
- Re: [patch/rfc] How to handle stepping into an unresolved plt entry?
  - From: Randolph Chung
- Re: [patch/rfc] How to handle stepping into an unresolved plt entry?
  - From: Andrew Cagney

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