9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hugo rivera <uair00@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] drawterm crash
Date: Wed,  1 Apr 2009 11:02:50 +0200	[thread overview]
Message-ID: <138575260904010202u653c289ctcc2c6b3149b3467f@mail.gmail.com> (raw)
In-Reply-To: <5859c57f4e27661221048bebc7aef95c@quanstro.net>

yes, I am on suse 10.0 x86_64.
When I compile I get two warnings related to longs and ints:
devtls.c:521: warning: comparison is always true due to limited range
of data type
sysproc.c:14: warning: cast to pointer from integer of different size
the first one points to
       if(d->mode != ~0UL)
which I have no idea why is causing a warning, since mode is also a ulong.
And the second one is from a cast
status = (char*)arg[0];
but I am not really sure how to fix this correctly. I just did something like
char c;
c = arg[0] & 0xFF;
status = &c;
this eliminates the warning and drawterm doesn't crash any more. But
the problem is that I cannot paste anything that comes from X to
drawterm, should I be able to?
Saludos

2009/3/31, erik quanstrom <quanstro@quanstro.net>:
> On Tue Mar 31 12:14:49 EDT 2009, uair00@gmail.com wrote:
>  > Hi,
>  > Just try to paste anything coming from X. (e.g. paint some text from
>  > an xterm, then try to paste it on some terminal on drawterm, using the
>  > menu or the 1-3 mouse chord, both crash anyway)
>
>
> you're using a 64-bit os, aren't you?  if that's the case, i fixed this a week
>  or so ago and pushed the patch to russ.  i think he's got the fix.  if not,
>  just fix the compile warning and you'll be good-to-go.  it's an int vs. long
>  issue.  unfortunately, i don't have yesterday for linux and don't remember
>  what i fixed.
>
>
>  - erik
>
>


--
Hugo



  reply	other threads:[~2009-04-01  9:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 16:12 hugo rivera
2009-03-31 16:26 ` erik quanstrom
2009-04-01  9:02   ` hugo rivera [this message]
2009-04-01  9:09     ` hugo rivera

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=138575260904010202u653c289ctcc2c6b3149b3467f@mail.gmail.com \
    --to=uair00@gmail.com \
    --cc=9fans@9fans.net \
    /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).