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] |
Any / all of the above.Basically removing _initialize_gdbtk from init.c does not prevent gdb from compiling, so the only reason why I didn't send a patch proposal is that I don't know the correct way of fixing it? Maybe separate init.c into init.c and insight-init.c? But there might be better solutions?
I believe the proper way to do this (Andrew/others will step in and tell me if I'm barking up the wrong perverbial tree) is to create an init_chain, which holds callbacks to be made for initialization. insight-main.c could register _initialize_gdbtk to this chain and top.c would then call it when it was doing initializations. My initial plan was to submit a patch to do just this. Eventually we could investigate getting other initializations registered in main (or we could simple keep init.c).
Or we could just create a new initialize_hook (yich) which main could set to get _initialize_gdbtk to run. Or we could just integrate _initialize_gdbtk into main(), or ...
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |