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] |
In this thread?Kris,In the past there was a proposal (patch?) to add a configuration time option that would specify a system init file. There was a patch. I believe that the actual idea was accepted as sound but the patch was lost in the paper trail :-( Can I suggest extending your patch so that the mechanism and file are specified at configure time (please don't ask me which of --with or --use or --... is the correct option :-).One problem with this (as Felix suggested earlier) is dealing with a gdb which supports multiple targets. The whole point is to be able to have per-target init files and hard wiring it in loses that. Specifying at config time would be okay for enable/disable but I think it would be better to have some sort of system of nomenclature for extra init files.
To clarify something here, target and architecture are separate but very related. GDB configured for a certain TARGET, will support one or more architectures. The x86-64, for instance, also supports i386.Here's a question: does a multi-targetted gdb know what it's targetting at the point of reading the .gdbinit or is this determined later? Is it switchable per session? I'm thinking that another possibility is to have it check for .gdbinit-$TARGET at the time that the target is determined.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |