colinux-devel

[coLinux-devel] Crash caused by vi.

[Clemmitt M. S. <sig...@bl...>]

Hi,

Sonnie Hook triggered an apparent bug using vi to edit his 
/etc/apt/sources.list file.  He posted a report to the Help
forum and I decided to see if I could recreate it.  I can :^P

If you edit a file with vi (doesn't matter what file except I
only tried plain text files, of course) you can reproduce the
crash by going into insert mode, moving the cursor to the
top-leftmost position, then typing the character '#'.  I've
gotten a few crash messages such as these:

----------------------------------------------------------------------
     50 [main] colinux-console-fltk 1384 handle_exceptions: Exception: 
STATUS_ACCESS_VIOLATION
  36173 [main] colinux-console-fltk 1384 open_stackdumpfile: Dumping stack 
trace to colinux-console-fltk.exe.stackdump
co_message_switch: freeing rule for 6
daemon: module disconnected: console
----------------------------------------------------------------------
     52 [main] colinux-console-fltk 1124 handle_exceptions: Exception: 
STATUS_ACCESS_VIOLATION
  33449 [main] colinux-console-fltk 1124 open_stackdumpfile: Dumping stack 
trace to colinux-console-fltk.exe.stackdump
co_os_daemon_thread() error [ 6 , RE0001 ]
co_message_switch: freeing rule for 6
daemon: module disconnected: console
----------------------------------------------------------------------

I've attached the stackdump from the first error above for your
perusal.  Please let me know if I can help look at this any
further.  And thanks to Sonnie :^)

					Clemmitt Sigler

Re: [coLinux-devel] Crash caused by vi.

[Clemmitt M. S. <sig...@bl...>]

Hi again,

On Mon, 22 Mar 2004, Clemmitt M. Sigler wrote:
> If you edit a file with vi (doesn't matter what file except I
> only tried plain text files, of course) you can reproduce the
> crash by going into insert mode, moving the cursor to the
> top-leftmost position, then typing the character '#'.

My apologies!  I forgot to post my config info.  Sorry.

Running coLinux snapshop 20040319-bin on the Debian-3.0r0.ext3.1gb
image.  Mounting the root filesystem image and a swap device image.
I've set my networking up for a static IP address of 192.168.0.40.
No other special configuration that I can think of (but I could be
wrong).  Please let me know if you have any questions.

					Clemmitt

Re: [coLinux-devel] Crash caused by vi.

[Olivier S. <co...@a-...>]

----- Original Message -----
From: "Clemmitt M. Sigler" <sig...@bl...>
To: <col...@li...>
Sent: Monday, March 22, 2004 4:53 PM
Subject: [coLinux-devel] Crash caused by vi.


> Hi,
>
> Sonnie Hook triggered an apparent bug using vi to edit his
> /etc/apt/sources.list file.  He posted a report to the Help
> forum and I decided to see if I could recreate it.  I can :^P
>
> If you edit a file with vi (doesn't matter what file except I
> only tried plain text files, of course) you can reproduce the
> crash by going into insert mode, moving the cursor to the
> top-leftmost position, then typing the character '#'.  I've
> gotten a few crash messages such as these:


confirmed, I just got it under gentoo, while editing a file.


I was at top-left corner of the colinux-console-fltk window but in the
middle of a file, then I was punching some 'x'.


the version I use is colinux-20040319-bin.tar.gz, not patched or rebuild.


O. Souiry

Re: [coLinux-devel] Crash caused by vi.

[Dan A. <da...@co...>]

On Mon, Mar 22, 2004 at 10:53:44AM -0500, Clemmitt M. Sigler wrote:

> Sonnie Hook triggered an apparent bug using vi to edit his 
> /etc/apt/sources.list file.  He posted a report to the Help
> forum and I decided to see if I could recreate it.  I can :^P
> 
> If you edit a file with vi (doesn't matter what file except I
> only tried plain text files, of course) you can reproduce the
> crash by going into insert mode, moving the cursor to the
> top-leftmost position, then typing the character '#'.  I've
> gotten a few crash messages such as these:

Okay, this was just a console code bug (it doesn't bring down
the coLinux system, though). Considered it fixed in the next 
snapshot/release.

-- 
Dan Aloni
da...@co...