This is the mail archive of the gdb-patches@sourceware.cygnus.com mailing list for the GDB project. See the GDB home page for more information.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
>target-architectures during startup, it would probably be more prudent to leave >most of that task until the point where GDB knew exactly which architecture was >being debugged. Yes, and this sounds like an example where multi-level initialization is a Good Thing(TM). I would love it if more things in GDB were "constructored" and not #define'd or hardcoded. Right now (read 4.17) with many remote targets you can't know the exact register list until you probe the target to find out what it is, yet the reg_names[] array is statically initialized (because on ptrace unix platforms that Just Worked), and we're just lucky that the rest of GDB adapts well to having reg_names[] edited after initialization. -- Todd Whitesel toddpw @ wrs.com