This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Re: Patch: --enable-profiling
- To: tromey at cygnus dot com
- Subject: Re: Patch: --enable-profiling
- From: Stan Shebs <shebs at cygnus dot com>
- Date: Mon, 1 Nov 1999 13:27:33 -0800
- CC: tromey at cygnus dot com, gdb-patches at sourceware dot cygnus dot com
Date: Sun, 31 Oct 1999 07:04:57 -0800 (PST)
From: Tom Tromey <tromey@cygnus.com>
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.
If it's not going to work, or as cgf suggests, it won't be very
interesting, it's worth just having a note in the docs to that effect.
Internals manual only is sufficient. Even a knowledgeable person,
using this for the first time, will be hard-pressed to know whether
the failure to build/run is a known limitation, or something wrong in
the setup.
Stan