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/rfc] Don't complain about unknown OSABI


On Wed, Aug 21, 2002 at 01:08:39PM -0400, Daniel Jacobowitz wrote:

 > Trying to code for edge cases that can't exist yet leads to sloppiness,
 > in my opinion.  Those cases should be dealt with when we have the means
 > to build a GDB supporting more than one processor family, and someone
 > adds per-architecture OS/ABIs.
A patch to include more than one architecture into a single gdb was posted a year ago :-)

FWIW, I agree 100% with Daniel.
Code isn't the problem here. It's the user-gdb interface. Does the the user model still work if there is more than one architecture. Not exploring the user-gdb interaction and instead just hacking code is how we came to have all the CLI querks we've come to hate :-)

Anyway, I suspect just forcing the architecture when the OSABI is changed is the most robust approach:

(gdb) set osabi MIPS/GNU/Linux
Current architecture is NS32K, change to MIPS? (y or n)
``the user is always right'' (no matter how silly it is :-).

I think it is also becomming aparent that there are several OSABI involved:

- the global default
- the current instance

``set osabi'' would change the current instance.

enjoy,
Andrew



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