public inbox for
help / color / mirror / Atom feed
Subject: insight/223: Segfault when scrolling after debugged program segfaults
Date: Mon, 05 May 2003 04:23:00 -0000	[thread overview]
Message-ID: <> (raw)

>Number:         223
>Category:       insight
>Synopsis:       Segfault when scrolling after debugged program segfaults
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon May 05 04:23:00 UTC 2003
>Originator:     Dominic C.
>Release:        insght-5.3
argv    ()
cdpath  /home/dcerquet
cwd     /home/dcerquet/polyphase/part4
dirstack        /home/dcerquet/polyphase/part4
echo_style      both
gid     xxxxx
group   xxxxx
history 100
home    /home/dcerquet
owd     /home/dcerquet/polyphase
path    (/usr/local/bin /usr/bin /bin /usr/bin/X11 /usr/games /home/dcerquet/bin .)
prompt  %U%m%u:%B%~%b%# 
prompt2 %R? 
prompt3 CORRECT>%R (y|n|e|a)? 
shell   /usr/bin/tcsh
shlvl   4
status  0
tcsh    6.09.00
term    xterm
tty     xxxxxx
uid     xxxxxx
user    xxxxxx
version tcsh 6.09.00 (Astron) 1999-08-16 (i386-intel-linux) options 8b,nls,bye,al,ng,rh,nd,color
When attempting to debug a progam of mine, it seems that after I am stopped and the (debugged) program has crashed, at random times directly afterwards when clicking on the scrollbar on the left, either the arrows or the bar itself, segfaults insight.

im running this under debian 2.2, kinda old..

ill see if i can get an exact test case where this will be workable, or at least more info on where its dying.


                 reply	other threads:[~2003-05-05  4:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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