9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sergey Reva <rs-rlab@narod.ru>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] windows drawterm bad access
Date: Sun, 30 Dec 2007 02:34:32 +0200	[thread overview]
Message-ID: <1453752796.20071230023432@narod.ru> (raw)
In-Reply-To: <00616f3c0a2b1afc06adce84ff3eccae@coraid.com>

Hello Erik and 9fans

Saturday, December 29, 2007, 6:22:00 PM, Erik wrote:
eq> when typing ^d at nedmail in hold mode,
eq> drawterm has faulted twice at 0x27fc0 with
eq> error code 0xc0000005.  unfortunately i have
eq> no tools to debug this.
eq> - erik

look like windows sources of drawterm broken long time ago, at least i
think so hour ago..

i have made some changes with just downloaded source and got "look like work
version" (at least it's say "cannot read authenticator in p9sk1" as my working drawterm
did). My plan 9 installation now far from me (i am at home for
holidays) so I can't try it right now (maybe i will install on vmware tomorrow)

There is 3 files
Make.win32 - adjusted to my working environment
lib/lib.h - #define uintptr unsigned int (should be ptr?)
kern/win32.c - undefined variable 'p' at showfilewrite(char *a, int n)

changes marked - "// by rlab"

result at http://rlab.org.ua/files/ndraw.zip

Now get other question:
How debug with mingw environment? Or get 'pdb' file from ld, i think
that should help...

I will search answers tomorrow... good night :)

-- 
Best regards,                      http://rlab.org.ua/
 Sergey                            mailto:rs-rlab@narod.ru


  parent reply	other threads:[~2007-12-30  0:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-29 16:22 erik quanstrom
2007-12-29 20:08 ` Steve Simon
2007-12-30  0:34 ` Sergey Reva [this message]
2007-12-30  1:39   ` Skip Tavakkolian
     [not found]   ` <bf45c7d0ab17ee0f284c263ebb46e696@9netics.com>
2007-12-30 14:40     ` Sergey Reva
2007-12-30 18:18       ` Skip Tavakkolian

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=1453752796.20071230023432@narod.ru \
    --to=rs-rlab@narod.ru \
    --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).