HP3000-L Archives

June 1997, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Goetz Neumann <[log in to unmask]>
Reply To:
Date:
Fri, 13 Jun 1997 23:30:08 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
[log in to unmask] wrote:
>
> Since I'm an egg in these matters:
> Is there any performance-issues involved when running a program compiled
> with symbolic debugger info? Am I to expect poor respons or 'system
> degradation' if the production runs 'xdb'-programs?

Basic answer is yes.

Programs compiled and linked for XDB's use contain special breakpoints
after each line of your programming languages source code (in between
the actual multiple RISC instructions that are the binary machine
code for one source statement) for source single stepping.

For each such breakpoint instuction the debugger gets invoked and
looks up some breakpoint table for whatever breakpoints you might
have set or to just give control back to your XDB session. Even
if you run the program w/o XDB it will do the lookup, just to find
out there are no breakpoints set.

It gets even worse if you have multiple instances of such a binary
running on the system, because they content (semaphore locking)
for the breakpoint table and will be blocked for a while.

hope this helps,

Goetz (normally [log in to unmask])

ATOM RSS1 RSS2