Path: utzoo!attcan!uunet!husc6!ukma!nrl-cmf!ames!pasteur!cory.Berkeley.EDU!dheller From: dheller@cory.Berkeley.EDU (Dan Heller) Newsgroups: comp.windows.x Subject: Re: "segmentation erroron Sun" Summary: out of core. Message-ID: <6366@pasteur.Berkeley.EDU> Date: 12 Oct 88 04:39:33 GMT References: <8810101619.AA19823@ti.com> Sender: news@pasteur.Berkeley.EDU Reply-To: dheller@cory.Berkeley.EDU.UUCP (Dan Heller) Organization: University of California, Berkeley Lines: 19 In article <8810101619.AA19823@ti.com> kral@skvax1.csc.ti.COM writes: > I have a bug in my X application that seems to appear randomly when I >run my application on a Sun 3/60 and appears not-so-randomly on a Sun 4/110. >The error is a segmentation violation. When I debug with dbx it says it >blows up in XrmStringToQuark. The error occurs when creating certain widgets If someone where I work didn't just have this exact same problem, I would have immediately agreed with Ralf Swick's reponse (that you're stepping on memory somewhere). Altho you actually could be stepping on memory as he suggests, in our particular case the problem was due to your workstation running out of memory. The Xlib stuff rarely checks for null returns from malloc calls (based on my experience reading the code). Our experience with the problem you described happened on a sun 3/50 -- when trying to run the program on another machine, it worked fine. Just the 3/50 had problems. It turned out to be out of memory. Ironic how our program died in the same place. If that's not the problem -- oh well.. Dan Heller