public inbox for
help / color / mirror / Atom feed
From: Avi Gozlan <>
Subject: RE: insight/341: insight crashes when defining pending breakpoint
Date: Tue, 07 Jul 2009 06:53:00 -0000	[thread overview]
Message-ID: <> (raw)

The following reply was made to PR insight/341; it has been noted by GNATS.

From: Avi Gozlan <>
To: "" <>,
        Avi Gozlan
        "" <>,
        "" <>,
        "" <>
Cc: Avi Gozlan <>
Subject: RE: insight/341: insight crashes when defining pending breakpoint
Date: Tue, 7 Jul 2009 09:49:39 +0300

 I would be thankful if you could supply download details for a stable snaps=
 hot of insight 6.8.
 I got to
 Yet I don't know if the latest weekly snapshot is stable.=20
 Also, what's the relation between the tcltk and insight tarballs? As far as=
  I remember, in the original insight 6.8 tarball both were located in the s=
 ame file... Should I simply tar xvf both to have them under the same src di=
 rectory? Would configure handle both trees correctly?
 Thanks a lot,
 -----Original Message-----
 From: []=20
 Sent: Thursday, July 02, 2009 6:30 PM
 To: Avi Gozlan;;; nobody@s=
 Subject: Re: insight/341: insight crashes when defining pending breakpoint
 Synopsis: insight crashes when defining pending breakpoint
 Responsible-Changed-From-To: unassigned->keiths
 Responsible-Changed-By: kseitz
 Responsible-Changed-When: Thu Jul  2 15:29:39 2009
 State-Changed-From-To: open->feedback
 State-Changed-By: kseitz
 State-Changed-When: Thu Jul  2 15:29:39 2009
     If you are using 6.8, I've attached a patch that was committed in Sept =
 to fix this. Otherwise, I recommend grabbing a CVS or a snapshot (which I w=
 ill do a better job of posting).
 Scanned by Check Point Total Security Gateway.

             reply	other threads:[~2009-07-07  6:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07  6:53 Avi Gozlan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-07-02 15:29 kseitz
2009-07-02 12:13 avi

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:

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

  git send-email \ \ \ \ \

* 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).