From: Alan Minga <aminga@cray.com>
Subject: SEGV in Garbage collection during build
Date: Wed, 20 Oct 2004 08:04:51 -0500 [thread overview]
Message-ID: <cl5p13$kse$1@flapjack.cray.com> (raw)
All,
I am porting emacs 21.3 to a cray X1 system and I'm having some
difficulties in building the code.
The build proceeds OK with only a few warning messages about type
such as
CC-180 cc: WARNING File = frame.c, Line = 1875
The indicated argument is incompatible with the corresponding formal
parameter.
STRING_BYTES (XSTRING (f->name))))
^
And
CC-513 cc: WARNING File = frame.c, Line = 2118
A value of type "unsigned char *" cannot be assigned to an entity of type
"char *".
color_name = XSTRING (value)->data;
But I don't believe these are significant.
The problem occurs in the build when emacs tries to load lisp. This
problem is reproducable by running
./temacs -batch
There is a failure in mark_object after it is recutsivly called about
for the 31,000th time. It makes stack tracing a bit difficult.
Attempst to print the Lisp variables result in the following error. I'm
not sure if that's due to an additional bug in print or if that's just
because the stack is so corrupted.
CC-513 cc: WARNING File = frame.c, Line = 2118
A value of type "unsigned char *" cannot be assigned to an entity of type
"char *".
color_name = XSTRING (value)->data;
So any suggestions for getting to the bottom of this SEGV?
------------
Alan Minga, Ph.D.
Sr. Presales Analyst
Cray Inc.
Breakpoint 1 at 0x1123364: file /ptmp/aminga/emacs-21.3/src/emacs.c,
line 387.
#0 0x12635ac in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4366
#1 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#2 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#3 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#4 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#5 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#6 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#7 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#8 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#9 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#10 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#11 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#12 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#13 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#14 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#15 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#16 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#17 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#18 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#19 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#20 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
#21 0x1263e28 in mark_object () at /ptmp/aminga/emacs-21.3/src/alloc.c:4628
...
#31747 0x1263e28 in mark_object () at
/ptmp/aminga/emacs-21.3/src/alloc.c:4628
#31748 0x1263e28 in mark_object () at
/ptmp/aminga/emacs-21.3/src/alloc.c:4628
#31749 0x1264d98 in mark_object () at
/ptmp/aminga/emacs-21.3/src/alloc.c:4616
#31750 0x1261430 in Fgarbage_collect () at
/ptmp/aminga/emacs-21.3/src/alloc.c:4097
#31751 0x12bdb58 in Feval () at /ptmp/aminga/emacs-21.3/src/eval.c:1912
#31752 0x131a9cc in readevalloop () at
/ptmp/aminga/emacs-21.3/src/lread.c:1259
#31753 0x1317568 in Fload () at /ptmp/aminga/emacs-21.3/src/lread.c:832
#31754 0x12be32c in Feval () at /ptmp/aminga/emacs-21.3/src/eval.c:2027
#31755 0x131a9cc in readevalloop () at
/ptmp/aminga/emacs-21.3/src/lread.c:1259
#31756 0x1317568 in Fload () at /ptmp/aminga/emacs-21.3/src/lread.c:832
#31757 0x12be32c in Feval () at /ptmp/aminga/emacs-21.3/src/eval.c:2027
#31758 0x1130214 in top_level_2 () at
/ptmp/aminga/emacs-21.3/src/keyboard.c:1254
#31759 0x12b8e4c in internal_condition_case () at
/ptmp/aminga/emacs-21.3/src/eval.c:1267
#31760 0x1130404 in top_level_1 () at
/ptmp/aminga/emacs-21.3/src/keyboard.c:1262
#31761 0x12b7834 in internal_catch () at
/ptmp/aminga/emacs-21.3/src/eval.c:1030
#31762 0x112fe3c in command_loop () at
/ptmp/aminga/emacs-21.3/src/keyboard.c:1228
#31763 0x112e57c in recursive_edit_1 () at
/ptmp/aminga/emacs-21.3/src/keyboard.c:950
#31764 0x112ec28 in Frecursive_edit () at
/ptmp/aminga/emacs-21.3/src/keyboard.c:1006
#31765 0x1129a2c in main () at /ptmp/aminga/emacs-21.3/src/emacs.c:1535
~
next reply other threads:[~2004-10-20 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 13:04 Alan Minga [this message]
2004-10-20 13:56 ` SEGV in Garbage collection during build Stefan Monnier
2004-10-20 18:59 ` Alan Minga
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='cl5p13$kse$1@flapjack.cray.com' \
--to=aminga@cray.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.