| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Joseph S <jks(at)selectacast(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: redhat debug info |
| Date: | 2007-03-28 19:21:50 |
| Message-ID: | 20070328192150.GA14174@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Mar 28, 2007 at 02:16:55PM -0400, Joseph S wrote:
> I thought the performance penalty came from making the executable
> bigger, which means the executor has to skip over the debug symbols
> somehow, which eats up cpu. If the symbols are in a different file this
> wouldn't apply.
When running the executable is mmaped into memory. So any extra data in
the executable has absolutly zero effect.
> Well I don't really know how debug symbols work. It seems that maybe
> all the debug info is is the source files with some mappling info then
> maybe it might.
No, the info is in the debug info (gdb can't be expected to understand
the source of every language you might want to debug).
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joseph S | 2007-03-28 19:41:32 | Re: redhat debug info |
| Previous Message | Nik | 2007-03-28 18:35:48 | pg_dump is stuck |