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] |
> Some global symbols are defined in gdb/main.c (eg. gdb_stdout, > gdb-stderr, etc). As the result if I'm building all except main.c in > object library to use with some IDE that uses gdb for debugging > (rhide-1.4.7), I'm getting unresolved references. Um, wow. It never occurred to me that anyone would try that. Specifically, we can't include GCC-specific things like the constructor attribute in GDB's source code. Lots of people build GDB with compilers other than GCC. I'm not the GDB Maintainer --- that'd be Dr. Shebs --- but my feeling is that we don't want to get into maintaining GDB with this kind of application in mind. If we turn GDB into a library, we should do it right --- design an interface that makes sense, document the interface, make sure that future changes preserve the boundaries, etc. My guess is that that would be more work than we really want to take on. > An alternative idea could be duplicating init code and global > vrariables in rhide. I think this is your best bet.