public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: laurent.duperval@cgi.ca
To: Insight Mailing List <insight@sourceware.cygnus.com>
Subject: Re: It will be great if Insight will remember BP too
Date: Tue, 28 Mar 2000 05:27:00 -0000	[thread overview]
Message-ID: <200003281325.IAA02374@qc.bell.ca> (raw)
In-Reply-To: <38E074E3.A0688A0A@plris.com>

On 28 Mar, Leon Pollak wrote:
> Hello, gurus.
>     It will be great if Insight will remember breakpoints set in its
> last session when restarted too.
> Thanks ahead.
> 
> 
> leonp@plris.com
> 

Well, you can currently save the breakpoints, doesn't that help any? Of
course you have to restore your breakpoints but... I have another idea: one
of the things that annoys me most when debugging Tcl-based apps (i'm doing a
lot of this, have you noticed?) is the use of shared libs. If I set a
breakpoint when I run a program, that breakpoint disappears and cannot be
reset when the app is restarted, because gdb doesn't know where to find the
symbol (since it's not loaded yet). Is it possible to set a breakpoint in a
function and have gdb notice when that  function is loaded up? In other
words, set some unexisting breakpoints that *will* exist at some time during
program execution, wwithout having to interrupt the process that is being
debugged. It's one of the features of a Tcl script debugger I'm using and I
find it very handy. But then, Tcl is a whole 'nother beast.

L

-- 
Laurent Duperval                   "Montreal winters are an intelligence test,
CGI - SARM Project                        and we who are here have failed it."
Phone: (514) 350-3368                                            -Don Camilli
mailto:laurent.duperval@cgi.ca      Penguin Power!


  reply	other threads:[~2000-03-28  5:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-28  0:59 Leon Pollak
2000-03-28  5:27 ` laurent.duperval [this message]
2000-03-29 11:36   ` Jim Blandy
2000-03-29 12:07     ` laurent.duperval

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=200003281325.IAA02374@qc.bell.ca \
    --to=laurent.duperval@cgi.ca \
    --cc=insight@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).