From: cinap_lenrek@gmx.de
To: 9fans@cse.psu.edu
Subject: Re: [9fans] drawterm segfault
Date: Sun, 14 Oct 2007 01:10:40 +0200 [thread overview]
Message-ID: <4be04afe756cf8986d51ea23d1fb88fc@gmx.de> (raw)
In-Reply-To: <fd3a28dfcfcdd87d6be73877a399b650@sorosj.hd.free.fr>
[-- Attachment #1: Type: text/plain, Size: 163 bytes --]
could you make a stacktrace with gdb please?
% gdb drawterm drawterm.core
(gdb) bt
...
drawterm should have been compiled with debug
symbols.
cinap
[-- Attachment #2: Type: message/rfc822, Size: 3272 bytes --]
From: johnny@sorosj.hd.free.fr
To: 9fans@cse.psu.edu
Subject: [9fans] drawterm segfault
Date: Sat, 13 Oct 2007 12:55:56 +0200
Message-ID: <fd3a28dfcfcdd87d6be73877a399b650@sorosj.hd.free.fr>
Hi!
I've had a strange segfault with drawterm lately. This is with the latest binaries from swtch.com/drawterm.
I have both tried it on sunos and linux, and have the same segfault happen.
The segfault occurs when I'm using acme. I open 3 new windows, and boom, drawterm vanishes. The reammy strange part in it is that it only happens when I open three specific windows in a specific order.
1, start drawterm, using my auth+cpu+fs server at home
2, open an acme window in $home
2, enter directories src/johnny with right-click with mouse, then open file wc.c with right-click, at this point my drawterm window disappears and all I see in the terminal I started drawterm from is: Segmentation fault.
This strangely doesn't happen when I open any other directories, only if i open these in the specified order, when acme starts.
Cheers!
Johnny
next prev parent reply other threads:[~2007-10-13 23:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 10:55 johnny
2007-10-13 23:10 ` cinap_lenrek [this message]
2007-10-13 17:40 ` johnny
2007-10-13 17:51 ` Skip Tavakkolian
2007-10-13 18:32 ` andrey mirtchovski
2007-10-13 21:00 ` johnny
2007-10-14 0:19 ` erik quanstrom
2007-10-14 7:26 ` johnny
2007-10-14 8:10 ` Sander van Dijk
2007-10-14 9:09 ` johnny
2007-10-14 20:41 ` johnny
2007-10-14 1:52 ` cinap_lenrek
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=4be04afe756cf8986d51ea23d1fb88fc@gmx.de \
--to=cinap_lenrek@gmx.de \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).