This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Re: Patch: --enable-profiling
- To: Stan Shebs <shebs at cygnus dot com>
- Subject: Re: Patch: --enable-profiling
- From: Tom Tromey <tromey at cygnus dot com>
- Date: Sun, 31 Oct 1999 07:04:57 -0800 (PST)
- Cc: tromey at cygnus dot com, gdb-patches at sourceware dot cygnus dot com
- References: <87u2n97vaa.fsf@cygnus.com><199910300045.RAA15367@andros.cygnus.com>
>>>>> "Stan" == Stan Shebs <shebs@cygnus.com> writes:
Stan> You should add a note to gdb/NEWS, a mention of
Stan> --enable-profiling somewhere in the internals manual (perhaps
Stan> connected to the section on coding, but I don't have a strong
Stan> preference), and a mention in the main GDB manual, with the rest
Stan> of the maintenance commands.
Will do.
Stan> Connected with the last, I'd like you to make the command exist
Stan> unconditionally, but if --enable-profiling wasn't used, to say
Stan> something "This GDB executable was not compiled with -pg" or
Stan> some such, rather than having a documented command be
Stan> mysteriously absent, with no explanation as to why.
Ok.
Stan> BTW, will this work with djgpp and/or cygwin? What will happen
Stan> if you try to configure on those with --enabling-profiling?
It might work or it might not. I don't know. My theory is that
profiling gdb is a maintainer thing, and if somebody uses
--enable-profiling and it doesn't build, they had better know what
they are doing anyway. We can always add tests for functions later.
I could add them now if it is important; it is easy enough to do.
Ordinarily I'm zealous about portability, but in this case I don't
think it matters that much.
Tom