GNU bug report logs - #35542
Installer does not display full backtrace on error

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 35542 in the body.
You can then email your comments to 35542 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de>
To: bug-guix <at> gnu.org
Subject: Installer does not display full backtrace on error
Date: Fri, 3 May 2019 10:59:27 +0200

When the Newt installer displays a backtrace, it is possible to scroll
up and down, but not left and right.  This cuts off important error
messages.

Message #8 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: Danny Milosavljevic <dannym <at> scratchpost.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de>
Cc: 35542 <at> debbugs.gnu.org
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Fri, 3 May 2019 11:40:19 +0200

[Message part 1 (text/plain, inline)]

On Fri, 3 May 2019 10:59:27 +0200
"pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de> wrote:

> When the Newt installer displays a backtrace, it is possible to scroll
> up and down, but not left and right.  This cuts off important error
> messages.

IMO the better solution would be to wrap the text--and not to add another
scrollbar.

It might help to change gnu/installer/newt/page.scm's run-file-textbox-page
so that it uses make-reflowed-textbox instead of make-textbox in file-textbox.

(I have no idea how to test that, though)

[Message part 2 (application/pgp-signature, inline)]

Message #11 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: "pelzflorian \(Florian Pelz\)" <pelzflorian <at> pelzflorian.de>
Cc: 35542 <at> debbugs.gnu.org, Mathieu Othacehe <m.othacehe <at> gmail.com>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Fri, 03 May 2019 12:09:24 +0200

"pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de> skribis:

> When the Newt installer displays a backtrace, it is possible to scroll
> up and down, but not left and right.  This cuts off important error
> messages.

Not sure if this can be fixed.  Mathieu?

The backtrace is kept in /tmp though.

Ludo'.

Message #14 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: Mathieu Othacehe <m.othacehe <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 35542 <at> debbugs.gnu.org,
 "pelzflorian \(Florian Pelz\)" <pelzflorian <at> pelzflorian.de>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Fri, 03 May 2019 14:15:27 +0200

Hey,

> Not sure if this can be fixed.  Mathieu?

The textbox object used for the backtrace window only supports vertical
scrolling. However, the text should be broken in lines that fit the box
horizontally, I'll try to find why it doesn't work.

Mathieu

Message #17 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: "pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de>
To: Mathieu Othacehe <m.othacehe <at> gmail.com>
Cc: 35542 <at> debbugs.gnu.org, Ludovic Courtès <ludo <at> gnu.org>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Fri, 3 May 2019 19:46:33 +0200

On Fri, May 03, 2019 at 02:15:27PM +0200, Mathieu Othacehe wrote:
> 
> Hey,
> 
> > Not sure if this can be fixed.  Mathieu?
> 
> The textbox object used for the backtrace window only supports vertical
> scrolling. However, the text should be broken in lines that fit the box
> horizontally, I'll try to find why it doesn't work.
> 
> Mathieu

I believe I read about Guile error messages not doing line wrapping in
terminals on the Guix or Guile mailing lists recently, but I cannot
find it.  Proper line wrapping may be the better solution.

Message #20 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: Mathieu Othacehe <m.othacehe <at> gmail.com>
To: "pelzflorian \(Florian Pelz\)" <pelzflorian <at> pelzflorian.de>
Cc: 35542 <at> debbugs.gnu.org, Ludovic Courtès <ludo <at> gnu.org>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Sat, 04 May 2019 11:43:28 +0200

[Message part 1 (text/plain, inline)]

Hello,

> I believe I read about Guile error messages not doing line wrapping in
> terminals on the Guix or Guile mailing lists recently, but I cannot
> find it.  Proper line wrapping may be the better solution.

In fact the textbox where the backtrace is displayed isn't doing any
line wrapping. The attached patch fixes the issue.

Thanks,

Mathieu

[0001-installer-Reflow-run-file-textbox-page-text.patch (text/x-diff, inline)]

From f68ded2f134d55c20f98300c0514c4fc18cd1d50 Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe <m.othacehe <at> gmail.com>
Date: Sat, 4 May 2019 11:33:33 +0200
Subject: [PATCH] installer: Reflow run-file-textbox-page text.

* gnu/installer/newt/page.scm (run-file-textbox-page): Reflow FILE-TEXT so
that it fits horizontally in the textbox.
---
 gnu/installer/newt/page.scm | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/gnu/installer/newt/page.scm b/gnu/installer/newt/page.scm
index 3173d54737..8a32c403df 100644
--- a/gnu/installer/newt/page.scm
+++ b/gnu/installer/newt/page.scm
@@ -559,7 +559,12 @@ ITEMS when 'Ok' is pressed."
                          '())))))
          (form (make-form)))
 
-    (set-textbox-text file-textbox file-text)
+    (set-textbox-text file-textbox
+                      (receive (_w _h text)
+                          (reflow-text file-text
+                                       file-textbox-width
+                                       0 0)
+                        text))
     (add-form-to-grid grid form #t)
     (make-wrapped-grid-window grid title)
 
-- 
2.17.1

Message #23 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: "pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de>
To: Mathieu Othacehe <m.othacehe <at> gmail.com>
Cc: 35542 <at> debbugs.gnu.org, Ludovic Courtès <ludo <at> gnu.org>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Sat, 4 May 2019 14:24:03 +0200

On Sat, May 04, 2019 at 11:43:28AM +0200, Mathieu Othacehe wrote:
> Hello,
> 
> > I believe I read about Guile error messages not doing line wrapping in
> > terminals on the Guix or Guile mailing lists recently, but I cannot
> > find it.  Proper line wrapping may be the better solution.
> 
> In fact the textbox where the backtrace is displayed isn't doing any
> line wrapping. The attached patch fixes the issue.
> 

I now get linewrapping, but provoked errors (these are not new bugs!)
are cut off like

In ./gnu/installer/keymap.scm
    163:7  8 (_ _)
In unknown file:
           7 (scm-error misc-error #f "~A" ("Unable to locate
keym…") …)

This seems like the same issue as Guile error backtraces only reaching
until the right end of the terminal and then getting cut off with
ellipses ….

I hope it is enough to guix pull from a Guix repo with the patch
applied and I do not get wrong output because I have not changed the
gnu/packages/package-management.scm Guix package to refer to a patched
version as well.

Regards,
Florian

Message #26 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: Danny Milosavljevic <dannym <at> scratchpost.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de>
Cc: 35542 <at> debbugs.gnu.org, Mathieu Othacehe <m.othacehe <at> gmail.com>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Sat, 4 May 2019 14:54:09 +0200

[Message part 1 (text/plain, inline)]

Hi,

On Sat, 4 May 2019 14:24:03 +0200
"pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de> wrote:

> I now get linewrapping, but provoked errors (these are not new bugs!)
> are cut off like
> 
> In ./gnu/installer/keymap.scm
>     163:7  8 (_ _)
> In unknown file:
>            7 (scm-error misc-error #f "~A" ("Unable to locate
> keym…") …)
> 
> This seems like the same issue as Guile error backtraces only reaching
> until the right end of the terminal and then getting cut off with
> ellipses ….

Oh, that again.  I've had it before and worked around it before.

Try

,use (system repl debug) ; or #:use-module (system repl debug)
(terminal-width 2000000)

f.e. at the top of gnu/installer.scm

[Message part 2 (application/pgp-signature, inline)]

Message #29 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: Mathieu Othacehe <m.othacehe <at> gmail.com>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 35542 <at> debbugs.gnu.org,
 "pelzflorian \(Florian Pelz\)" <pelzflorian <at> pelzflorian.de>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Sat, 04 May 2019 18:14:48 +0200

Hey,

> ,use (system repl debug) ; or #:use-module (system repl debug)
> (terminal-width 2000000)
>
> f.e. at the top of gnu/installer.scm

Thanks for testing Florian. Based on Danny suggestion we could set
COLUMNS to 200 to have a more verbose backtrace (like guix itself).

Using higher values, the backtrace becomes really long and harder to
read. WDYT?

Mathieu

Message #32 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: Mathieu Othacehe <m.othacehe <at> gmail.com>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 35542 <at> debbugs.gnu.org,
 "pelzflorian \(Florian Pelz\)" <pelzflorian <at> pelzflorian.de>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Sat, 04 May 2019 18:15:54 +0200

[Message part 1 (text/plain, inline)]

And the patch ...

Sorry,

Mathieu

[0001-installer-Increase-backtrace-verbosity.patch (text/x-diff, inline)]

From 3348df0c72e9bcdf31b63155d9c6bdbaee515524 Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe <m.othacehe <at> gmail.com>
Date: Sat, 4 May 2019 18:10:40 +0200
Subject: [PATCH] installer: Increase backtrace verbosity.

* gnu/installer.scm (installer-program): Set COLUMNS env variable to 200 to
make guile backtraces more verbose.
---
 gnu/installer.scm | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/gnu/installer.scm b/gnu/installer.scm
index fe2841397e..435cad507d 100644
--- a/gnu/installer.scm
+++ b/gnu/installer.scm
@@ -400,5 +400,9 @@ selected keymap."
        ;; some reason, unicode support is not correctly installed
        ;; when calling this in 'installer-builder'.
        (setenv "LANG" "en_US.UTF-8")
+       ;; Initialize 'terminal-width' in (system repl debug)
+       ;; to a large-enough value to make backtrace more
+       ;; verbose.
+       (setenv "COLUMNS" "200")
        (execl #$(program-file "installer-real" installer-builder)
               "installer-real"))))
-- 
2.17.1

Message #35 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: Danny Milosavljevic <dannym <at> scratchpost.org>
To: Mathieu Othacehe <m.othacehe <at> gmail.com>
Cc: 35542 <at> debbugs.gnu.org,
 "pelzflorian \(Florian Pelz\)" <pelzflorian <at> pelzflorian.de>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Sat, 4 May 2019 19:06:17 +0200

[Message part 1 (text/plain, inline)]

Hi Mathieu,

On Sat, 04 May 2019 18:14:48 +0200
Mathieu Othacehe <m.othacehe <at> gmail.com> wrote:

> Thanks for testing Florian. Based on Danny suggestion we could set
> COLUMNS to 200 to have a more verbose backtrace (like guix itself).

Good idea in principle.

> Using higher values, the backtrace becomes really long and harder to
> read. WDYT?

When we have a designed error message, we present one--and, there, brevity
is good.

But backtraces are for developers only anyway, and are not designed error
messages.
So for backtraces I'm against throwing *anything* of the backtrace
message away because we don't know what part of it is important (if we
did, we'd print a designed error message instead--I'm all for doing that).

I think this is something the default Guile setting gets wrong and I
don't understand how it can be a good idea to suppress half of a
message intended to simplify debugging for a developer "because it's
too long".  The length is nothing compared to the amount of text a
developer has to type in order to reproduce the missing parts later on,
if it's even possible.

I'm even actually using core files (including attaching to them using a
debugger in order to examine variable values), so I might be an outlier.

So I'd be for either presenting the entire backtrace or suppressing the
entire backtrace, not having teaser backtraces :)

[Message part 2 (application/pgp-signature, inline)]

Message #38 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: "pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de>
To: Mathieu Othacehe <m.othacehe <at> gmail.com>
Cc: 35542 <at> debbugs.gnu.org, Danny Milosavljevic <dannym <at> scratchpost.org>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Sat, 4 May 2019 19:26:47 +0200

On Sat, May 04, 2019 at 06:14:48PM +0200, Mathieu Othacehe wrote:
> Thanks for testing Florian. Based on Danny suggestion we could set
> COLUMNS to 200 to have a more verbose backtrace (like guix itself).
> 

It works (I have applied both patches).

This is one of the longer backtrace steps:

In ice-9/eval.scm:
    619:8 17 (_ #(#(#(#<directory (guile-user) 1775140>
#<<installer> name: newt init: #<procedure init ()> exit:
#<procedure exit ()> exit-error: #<procedure exit-error (file
key args)> fi…> …)) …))

Message #41 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: "pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 35542 <at> debbugs.gnu.org, Mathieu Othacehe <m.othacehe <at> gmail.com>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Sat, 4 May 2019 19:38:07 +0200

On Sat, May 04, 2019 at 07:06:17PM +0200, Danny Milosavljevic wrote:
> So I'd be for either presenting the entire backtrace or suppressing the
> entire backtrace, not having teaser backtraces :)

Let’s assume someone is getting an error in the installer for some
reason.  If they are Guix developers, maybe they understand the issue
from the (trimmed) backtrace.  If they are not well-versed in Unix,
with the backtrace they can exfiltrate the (trimmed) error with a
camera.  I hope I understand the purpose correctly.  Maybe it saves
the people on the mailing list complicated explanations.  These maybes
become more likely with a fuller backtrace, I suppose.

Regards,
Florian

Message #44 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: "pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 35542 <at> debbugs.gnu.org, Mathieu Othacehe <m.othacehe <at> gmail.com>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Sat, 4 May 2019 19:40:32 +0200

On Sat, May 04, 2019 at 07:38:07PM +0200, pelzflorian (Florian Pelz) wrote:
> On Sat, May 04, 2019 at 07:06:17PM +0200, Danny Milosavljevic wrote:
> > So I'd be for either presenting the entire backtrace or suppressing the
> > entire backtrace, not having teaser backtraces :)
> 
> Let’s assume someone is getting an error in the installer for some
> reason.  If they are Guix developers, maybe they understand the issue
> from the (trimmed) backtrace.  If they are not well-versed in Unix,
> with the backtrace they can exfiltrate the (trimmed) error with a
> camera.  I hope I understand the purpose correctly.  Maybe it saves
> the people on the mailing list complicated explanations.  These maybes
> become more likely with a fuller backtrace, I suppose.
> 

On the other hand the error message after the backtrace is hopefully
enough most of the time.  But maybe it is not.

Regards,
Florian

Message #47 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Mathieu Othacehe <m.othacehe <at> gmail.com>
Cc: 35542 <at> debbugs.gnu.org, Danny Milosavljevic <dannym <at> scratchpost.org>,
 "pelzflorian \(Florian Pelz\)" <pelzflorian <at> pelzflorian.de>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Wed, 08 May 2019 16:35:01 +0200

Hi Mathieu,

Mathieu Othacehe <m.othacehe <at> gmail.com> skribis:

> +       ;; Initialize 'terminal-width' in (system repl debug)
> +       ;; to a large-enough value to make backtrace more
> +       ;; verbose.
> +       (setenv "COLUMNS" "200")

What about instead doing something like this:

  (use-modules ((system repl debug) #:select (terminal-width)))

  (with-fluids ((terminal-width 200))
    …)

?

That would ensure we’re only changing Guile’s notion of the terminal
width and not interfering with other tools we might launch as child
processes.

Thoughts?

Ludo’.

Message #50 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: Mathieu Othacehe <m.othacehe <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 35542 <at> debbugs.gnu.org, Danny Milosavljevic <dannym <at> scratchpost.org>,
 "pelzflorian \(Florian Pelz\)" <pelzflorian <at> pelzflorian.de>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Tue, 14 May 2019 14:09:52 +0200

[Message part 1 (text/plain, inline)]

Hey Ludo,

> That would ensure we’re only changing Guile’s notion of the terminal
> width and not interfering with other tools we might launch as child
> processes.
>
> Thoughts?

Seems like a better idea indeed. Here's an update patch.

About using 200 or a much larger value as Danny suggested, I don't have
a strong opinion myself. WDYT?

Thanks,

Mathieu

[0001-installer-Increase-backtrace-verbosity.patch (text/x-diff, inline)]

From d5f792414d0666d554dc8c7b6fee351bbe7a1c14 Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe <m.othacehe <at> gmail.com>
Date: Tue, 14 May 2019 14:05:36 +0200
Subject: [PATCH] installer: Increase backtrace verbosity.

* gnu/installer.scm (installer-program): Set terminal-width to 200 to
make guile backtraces more verbose.
---
 gnu/installer.scm | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/gnu/installer.scm b/gnu/installer.scm
index 3dd76707bf..40c06af320 100644
--- a/gnu/installer.scm
+++ b/gnu/installer.scm
@@ -336,6 +336,8 @@ selected keymap."
                          (gnu services herd)
                          (guix i18n)
                          (guix build utils)
+                         ((system repl debug)
+                          #:select (terminal-width))
                          (ice-9 match))
 
             ;; Initialize gettext support so that installers can use
@@ -359,6 +361,11 @@ selected keymap."
             (bindtextdomain "xkeyboard-config"
                             #+(file-append xkeyboard-config "/share/locale"))
 
+            ;; Initialize 'terminal-width' in (system repl debug)
+            ;; to a large-enough value to make backtrace more
+            ;; verbose.
+            (terminal-width 200)
+
             (let* ((current-installer newt-installer)
                    (steps (#$steps current-installer)))
               ((installer-init current-installer))
-- 
2.17.1

Message #53 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: Danny Milosavljevic <dannym <at> scratchpost.org>
To: Mathieu Othacehe <m.othacehe <at> gmail.com>
Cc: 35542 <at> debbugs.gnu.org,
 "pelzflorian \(Florian Pelz\)" <pelzflorian <at> pelzflorian.de>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Tue, 14 May 2019 18:01:19 +0200

[Message part 1 (text/plain, inline)]

Hi Mathieu,

On Sat, 04 May 2019 11:43:28 +0200
Mathieu Othacehe <m.othacehe <at> gmail.com> wrote:

> Hello,
> 
> > I believe I read about Guile error messages not doing line wrapping in
> > terminals on the Guix or Guile mailing lists recently, but I cannot
> > find it.  Proper line wrapping may be the better solution.  
> 
> In fact the textbox where the backtrace is displayed isn't doing any
> line wrapping. The attached patch fixes the issue.

I've tested and applied that patch.

I've also fixed the btrfs problem.

I've also added fat16 support (there was ar report about it--although I
can't for the life of me find the associated bug report anymore).  Oh well,
should be an improvement.

All these things are available on guix master now.

[Message part 2 (application/pgp-signature, inline)]

Message #56 received at 35542 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Mathieu Othacehe <m.othacehe <at> gmail.com>
Cc: 35542 <at> debbugs.gnu.org, Danny Milosavljevic <dannym <at> scratchpost.org>,
 "pelzflorian \(Florian Pelz\)" <pelzflorian <at> pelzflorian.de>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Tue, 14 May 2019 23:02:01 +0200

Hi Mathieu,

Mathieu Othacehe <m.othacehe <at> gmail.com> skribis:

>> That would ensure we’re only changing Guile’s notion of the terminal
>> width and not interfering with other tools we might launch as child
>> processes.
>>
>> Thoughts?
>
> Seems like a better idea indeed. Here's an update patch.
>
> About using 200 or a much larger value as Danny suggested, I don't have
> a strong opinion myself. WDYT?

I think 200 is good.  You wouldn’t want the backtrace to be filled with
bytevectors, for instance.

Also, if people take pictures of their screen with a backtrace, I hope
there’ll still be enough stack frames on the picture.  :-)  With a large
‘terminal-width’, there’s a risk that a single frame would fill 10
lines.

> From d5f792414d0666d554dc8c7b6fee351bbe7a1c14 Mon Sep 17 00:00:00 2001
> From: Mathieu Othacehe <m.othacehe <at> gmail.com>
> Date: Tue, 14 May 2019 14:05:36 +0200
> Subject: [PATCH] installer: Increase backtrace verbosity.
>
> * gnu/installer.scm (installer-program): Set terminal-width to 200 to
> make guile backtraces more verbose.

LGTM!

Thank you,
Ludo’.

Message #61 received at 35542-done <at> debbugs.gnu.org (full text, mbox):

From: Mathieu Othacehe <m.othacehe <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 35542-done <at> debbugs.gnu.org, Danny Milosavljevic <dannym <at> scratchpost.org>,
 "pelzflorian \(Florian Pelz\)" <pelzflorian <at> pelzflorian.de>
Subject: Re: bug#35542: Installer does not display full backtrace on error
Date: Wed, 15 May 2019 09:30:16 +0200

Hey,

> I think 200 is good.  You wouldn’t want the backtrace to be filled with
> bytevectors, for instance.

Fine with me. Pushed.

Thanks for reviewing,

Mathieu

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.