This is the mail archive of the gdb-patches@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/rfa] Allow breakpoing to be added after inferior has started


The shlib-call.exp test fails on hppa (also ia64) because it tries to add a breakpoint before the inferior is started, so there's no where to put the breakpoint. gdb can handle this case if we allow pending breakpoints in the test.

this only works on x86 and some other architectures because they put
instructions into the plt; but some architectures put addresses in the
plt.

ok to commit?

This is sounding a lot like PIE (position independant executable): where it isn't possible to determine a breakpoint's true (re-located) location until after the inferior has started.


Can you describe the problem in more detail?

Andrew


2004-05-21 Randolph Chung <tausq@debian.org>

	* gdb.base/shlib-call.exp: Allow breakpoint to be added after inferior
	has started.



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