go to www.geomview.org home page
 
Home

Overview
FAQ
Documentation

Download

Mailing List

Geomview For Windows?

Support
Users
Development

Bug Reporting
Contributing
Contact Us

Sponsors

 

Site Search

 

Advanced
Search

 
About the software@geom archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Update REQ 5108]: bug in alpha version of 1.5 prelease?


  • To: software@geom
  • Subject: Re: [Update REQ 5108]: bug in alpha version of 1.5 prelease?
  • From: "Daeron Meyer" <daeron>
  • Date: Sun, 23 Oct 94 23:20:45 CDT

> Date: Sun, 23 Oct 1994 18:16:19 -0400 (EDT)
> From: Greg Griffin <ggriffin at cmbr.phys.cmu.edu>
> To: software@geom
> Subject: bug in alpha version of 1.5 prelease?
> Message-Id: <Pine.OSF.3.91.941023175333.27641A-100000 at cmbr.phys.cmu.edu>
> 
> 
> Hi there, I'm beta testing geomview prelease 1.5
> on a dec alpha.  I was previously running 1.4.1 (for 
> which precompiled alpha binaries were available) and 
> it worked fine. Getting core dumps now, could be a bug.
> 
> ----------------------------
> HERE'S WHAT HAPPENS with 1.5
> ----------------------------
> I run geomview and a blank camera window 
> flashes up briefly and then I get a core dump. 
> gdb "where" says: #0  XShmCreateImage () at XShm.c:327
> 
> something to do with the new use of X shared memory 
> extension?

Yes, most likely.

> -------------------------
> SOME INFO ABOUT OUR SETUP
> -------------------------
> dec alpha 3000/600 with 64 M of memory, OSF 1.3
> 
> I am using gnu make, but otherwise our compilation is pretty
> standard (using plain old cc). I also tried the suggestion of 
> setting MKFILEDIR = . and using the standard alpha make,
> but this gave: "Warning: CPU changed after being used"
> even though CPU = alpha is defined in the usual place.
> 
> Can mail you my mk.site.default and Makedefs.global
> but I just did the standard things. Can also mail
> you make.log, the >& output of make install, which went
> pretty smoothly (though there are a couple warnings that
> may or may not help you).
> 
> -Greg
> 
> 
> 

Hi Greg,

Yes, it is undoubtedly something to do with shared memory. I wonder if
there are two things you could do for us. First, if you have more than
one Dec Alpha, try running the program on one and bringing up the display
on another and see if it works. Also, try running it on an Alpha and
bringing up the display on a Sun or HP or anything besides the Alpha and
see if it works. Finally could you mail us the results of these tests as
well as the output of "xdpyinfo" for the Dec Alpha X server. It may take
a while to fix whatever is wrong with the Alpha version since we don't
have any of those machines here.

Thanks,
Daeron


 
Home | Overview | FAQ | Documentation | Support | Download | Mailing List
Windows? | Development | Bug Reporting | Contributing | Contact Us | Sponsors
 
site hosted by
SourceForge Logo