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: Extending corefile.exp to handle remote targets


I'm looking at testing the core dump functionality for CRIS (remote target, Linux-based). (The gcore functionality is not an option for a remote target, right?).

There's also auxv.exp and, to a lesser extent, bigcore.exp.


I've actually been thinking of submitting a patch that splits auxv.exp in two - separately test auxv with corefile. That way it's easier to differentiate between broken native and broken corefile auxv.

But what ever.

I was thinking I should extend corefile.exp to work with a remote target, probably adding a register restoration check, and possibly even unifying it with gcore.exp - or is there a reason for the difference between the two? On the surface it looks like the only difference is how the core file is generated.

Any hints or warnings before I proceed?

Watch out for BFD!


Writing cross core-files doesn't work because the relevant BFD code assumes HOST == TARGET :-(

It's been suggested that we [gdb] should instead implement our own local core file manipulation routines and bypass what's provided by BFD.

Andrew



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