From: Ryan Yeske <rcyeske@gmail.com>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Failure to build on OpenBSD macppc
Date: Wed, 02 May 2007 13:52:59 -0700 [thread overview]
Message-ID: <20070505010520.5C97A142E8@owie.lan> (raw)
In-Reply-To: <E1HjGY4-0004Ul-HL@fencepost.gnu.org>
Could you please try running temacs under GDB and starting
with `r temacs -batch loadup'? Please report the backtrace,
and then please try investigating the cause of the crash
by examining relevant data values in the innermost frame.
$ gdb ./temacs
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "powerpc-unknown-openbsd4.0"...
Environment variable "DISPLAY" not defined.
TERM = dumb
Breakpoint 1 at 0x187ad70: file sysdep.c, line 1383.
(gdb)
Starting program: /home/rcyeske/emacs/src/temacs temacs -batch loadup
Loading loadup.el (source)...
Using load-path (/home/rcyeske/emacs/lisp)
Loading emacs-lisp/byte-run (source)...
Loading emacs-lisp/backquote (source)...
Loading subr (source)...
Loading version.el (source)...
Loading widget (source)...
Loading custom (source)...
Loading emacs-lisp/map-ynp (source)...
Loading env (source)...
Loading cus-start (source)...
Loading international/mule (source)...
Loading international/mule-conf.el (source)...
Loading format (source)...
Loading bindings (source)...
Loading files.el (source)...
Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) #0 0x00000000 in ?? ()
#1 0x00000000 in ?? ()
Lisp Backtrace:
Cannot access memory at address 0x0
(gdb)
next prev parent reply other threads:[~2007-05-02 20:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 15:15 Failure to build on OpenBSD macppc Richard Stallman
2007-05-02 20:52 ` Ryan Yeske [this message]
2007-05-05 23:18 ` Richard Stallman
2007-05-06 0:01 ` Ryan Yeske
2007-05-06 1:35 ` Glenn Morris
2007-05-06 0:07 ` Ryan Yeske
-- strict thread matches above, loose matches on Subject: below --
2007-05-11 21:56 Richard Stallman
2007-05-13 21:50 ` Ryan Yeske
2007-05-13 22:20 ` Alfred M. Szmidt
2007-05-14 16:52 ` Richard Stallman
2007-05-14 9:52 ` Alfred M. Szmidt
2007-05-15 9:46 ` Richard Stallman
2007-05-15 17:07 ` Alfred M. Szmidt
2007-05-16 1:39 ` Richard Stallman
2007-05-16 7:55 ` Alfred M. Szmidt
2007-05-16 14:32 ` Richard Stallman
2007-05-16 14:47 ` David Kastrup
2007-05-16 15:04 ` Ryan Yeske
2007-05-16 15:51 ` Alfred M. Szmidt
2007-05-17 8:01 ` Glenn Morris
2007-05-17 8:42 ` Alfred M. Szmidt
2007-05-17 21:32 ` Richard Stallman
2007-05-16 16:26 ` Stefan Monnier
2007-05-16 19:38 ` Glenn Morris
2007-05-16 19:46 ` Alfred M. Szmidt
2007-05-14 16:52 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070505010520.5C97A142E8@owie.lan \
--to=rcyeske@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).