public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dave Lee <davel@canuck.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] xemacs segfault
Date: Mon, 8 Apr 2002 07:42:49 -0600	[thread overview]
Message-ID: <Pine.SGI.4.21.0204080736440.16551340-100000@the-gimp> (raw)
In-Reply-To: <uo1ydq978q.fsf@bashful.cdf.toronto.edu>


Arcady Genkin wrote:
> Dave Lee <davel@canuck.com> writes:
> 
> > Has anyone been able to figure out why xemacs segfaults on startup?  As
> > mentioned before, if you are emerge-ing something, than xemacs will
> > actually run w/o segfaulting.  This is strange behavior. TIA,  Dave
> 
> Which version?

both 21.1.whatever and 21.4.6

> Have you tried
> 
>   xemacs -debug-init
>   xemacs -vanilla
> 
> Also try running in the terminal with
> 
>   xemacs -nw

I did try -vanilla and -norc, but not the others.  I'll see what they do
for me.

> Perhaps these would help you to pin-point the problem...

I dont know, would it?  Can anybody see why xemacs would run just fine
when I am in the process of compiling something else, but when I am not
compiling anything it segfaults immediately.

I did try to run strace on xemacs, and although I dont have the results at
hand to cut and paste, the segfault was happening after a bunch of stat
calls that were looking for default.{elc,el,} but when I am compiling
something nothing happens here other than ENOENT.

Dave



  reply	other threads:[~2002-04-08 13:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-08  2:39 [gentoo-dev] xemacs segfault Dave Lee
2002-04-08  3:52 ` Arcady Genkin
2002-04-08 13:42   ` Dave Lee [this message]
2002-04-08 15:05     ` Naresh Donti
2002-04-08 15:40       ` Dave Lee
2002-04-08 20:24         ` [gentoo-dev] There is a Bug about this " Sloan Poe
2002-04-08 17:17   ` [gentoo-dev] " Dave Lee
     [not found] <20020408080203.7C2B520EEAEA@chiba.3jane.net>
2002-04-08 18:56 ` Stefan Jones

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=Pine.SGI.4.21.0204080736440.16551340-100000@the-gimp \
    --to=davel@canuck.com \
    --cc=gentoo-dev@gentoo.org \
    /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