Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: bstell@netscape.com (Brian Stell)
To: gdb_mailing_list <gdb@sources.redhat.com>
Subject: debugging mozilla with gdb is so slow
Date: Fri, 16 Feb 2001 21:39:00 -0000	[thread overview]
Message-ID: <3A8E0F7A.5C5334F1@netscape.com> (raw)

I find that using gdb to debug Mozilla very slow.

It is so slow that I find many (most?) Linux Mozilla 
developers use printfs because they "need to get work done".

My startup time (time to the first moz window) is really 
long when I use gdb:

  Mozilla no gdb:   11 sec
  Mozilla with gdb: 125 sec

This does not seem to meet the goal in the gdb docs:

    GDB should be responsive to the user.  A programmer 
    hot on the trail of a nasty bug, and operating under 
    a looming deadline, is going to be very impatient of 
    everything, including the response time to debugger
    commands.

( http://www.math.psu.edu/doc/emacs/info/gdbint.info-1 )

Gdb itself comes up fairly fast ~ 5-10 sec. This long
start delay makes it basically unusable.

I have a 500MHz P3 Linux Redhat 6.2 system with 512M ram.

Any thoughts?

Brian Stell


             reply	other threads:[~2001-02-16 21:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-16 21:39 Brian Stell [this message]
2001-02-16 21:54 ` Daniel Berlin
2001-02-19 14:07   ` Brian Stell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A8E0F7A.5C5334F1@netscape.com \
    --to=bstell@netscape.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox