unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Angelo Graziosi <angelo.graziosi@alice.it>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Problems with Emacs (Cygwin)
Date: Thu, 10 Apr 2008 10:10:04 +0200	[thread overview]
Message-ID: <47FDCB5C.6090008@alice.it> (raw)
In-Reply-To: <jwvhceafqbr.fsf-monnier+emacs@gnu.org>

Stefan Monnier ha scritto:
>> The Cygwin build of Emacs-CVS-23.0.60 (a few hours ago) fails when started
>> $ emacs -nw
>> Fatal error (11)Segmentation fault
> 
>> Instead, it works if started as
> 
>> $ emacs &
> 
>> With CVS of less than 24 hours ago all works fine.
> 
>> Could the cause be [1]?
> 
> Could be.  But we need more info to figure it out.
> E.g. a backtrace?
> 
> 
>         Stefan
> 

(You should consider I am not an expert of GDB...)

At [1] bt.

Cheers,
    Angelo.

---
[1] (Trying)Using GDB:
(gdb) emacs

(gdb) r -nw
Starting program: /usr/local/bin/emacs -nw
[New thread 2536.0x98c]
[New thread 2536.0x990]

Program received signal SIGSEGV, Segmentation fault.
set_tty_color_mode (tty=0x7d8600, f=0x736800)
     at /tmp.builds/emacs-23.0.60/src/term.c:2175
2175      tem = assq_no_quit (Qtty_color_mode, XFRAME (val)->param_alist);
(gdb)

(gdb) bt
#0  set_tty_color_mode (tty=0x7d8600, f=0x736800)
     at /tmp.builds/emacs-23.0.60/src/term.c:2175
#1  0x004340a1 in redisplay_internal (
     preserve_echo_area=<value optimized out>)
     at /tmp.builds/emacs-23.0.60/src/xdisp.c:11192
#2  0x00434e3d in echo_area_display (update_frame_p=1)
     at /tmp.builds/emacs-23.0.60/src/xdisp.c:9007
#3  0x004350f0 in message3_nolog (m=18390563, nbytes=111, multibyte=0)
     at /tmp.builds/emacs-23.0.60/src/xdisp.c:7871
#4  0x004352f0 in message3 (m=18390563, nbytes=111, multibyte=0)
     at /tmp.builds/emacs-23.0.60/src/xdisp.c:7806
#5  0x00519fef in Fmessage (nargs=2, args=0x22c2a4)
     at /tmp.builds/emacs-23.0.60/src/editfns.c:3381
#6  0x0052acb9 in Fy_or_n_p (prompt=18390707)
     at /tmp.builds/emacs-23.0.60/src/fns.c:2640
#7  0x0051e43c in Ffuncall (nargs=2, args=0x22c340)
     at /tmp.builds/emacs-23.0.60/src/eval.c:3025
#8  0x00549108 in Fbyte_code (bytestr=8328531, vector=11433988,
     maxdepth=<value optimized out>)
     at /tmp.builds/emacs-23.0.60/src/bytecode.c:679
#9  0x00520163 in funcall_lambda (fun=10073028, nargs=0, 
arg_vector=0x22c494)
     at /tmp.builds/emacs-23.0.60/src/eval.c:3212
#10 0x0051e150 in Ffuncall (nargs=1, args=0x22c490)
     at /tmp.builds/emacs-23.0.60/src/eval.c:3082
---Type <return> to continue, or q <return> to quit---
#11 0x00549108 in Fbyte_code (bytestr=18373971, vector=8482436,
     maxdepth=<value optimized out>)
     at /tmp.builds/emacs-23.0.60/src/bytecode.c:679
#12 0x00520163 in funcall_lambda (fun=10201092, nargs=0, 
arg_vector=0x22c5fc)
     at /tmp.builds/emacs-23.0.60/src/eval.c:3212
#13 0x0051e150 in Ffuncall (nargs=1, args=0x22c5f8)
     at /tmp.builds/emacs-23.0.60/src/eval.c:3082
#14 0x0051f421 in run_hook_with_args (nargs=1, args=0x22c5f8,
     cond=to_completion) at /tmp.builds/emacs-23.0.60/src/eval.c:2684
#15 0x0051f5cf in Frun_hooks (nargs=1, args=0x22c694)
     at /tmp.builds/emacs-23.0.60/src/eval.c:2547
#16 0x0051e2c6 in Ffuncall (nargs=2, args=0x22c690)
     at /tmp.builds/emacs-23.0.60/src/eval.c:3006
#17 0x00549108 in Fbyte_code (bytestr=6022755, vector=6022772,
     maxdepth=<value optimized out>)
     at /tmp.builds/emacs-23.0.60/src/bytecode.c:679
#18 0x00520163 in funcall_lambda (fun=6022732, nargs=0, arg_vector=0x22c7d4)
     at /tmp.builds/emacs-23.0.60/src/eval.c:3212
#19 0x0051e150 in Ffuncall (nargs=1, args=0x22c7d0)
     at /tmp.builds/emacs-23.0.60/src/eval.c:3082
#20 0x00549108 in Fbyte_code (bytestr=6019467, vector=6019484,
     maxdepth=<value optimized out>)
     at /tmp.builds/emacs-23.0.60/src/bytecode.c:679
#21 0x00520163 in funcall_lambda (fun=6019444, nargs=0, arg_vector=0x22c8a0)
---Type <return> to continue, or q <return> to quit---
     at /tmp.builds/emacs-23.0.60/src/eval.c:3212
#22 0x00520364 in apply_lambda (fun=6019444, args=7407617, eval_flag=1)
     at /tmp.builds/emacs-23.0.60/src/eval.c:3136
#23 0x0051fa24 in Feval (form=8272445)
     at /tmp.builds/emacs-23.0.60/src/eval.c:2416
#24 0x004bac73 in top_level_2 ()
     at /tmp.builds/emacs-23.0.60/src/keyboard.c:1383
#25 0x0051d790 in internal_condition_case (bfun=0x4bac60 <top_level_2>,
     handlers=7491753, hfun=0x4be4b0 <cmd_error>)
     at /tmp.builds/emacs-23.0.60/src/eval.c:1494
#26 0x004bd91d in top_level_1 ()
     at /tmp.builds/emacs-23.0.60/src/keyboard.c:1391
#27 0x0051d86a in internal_catch (tag=7487825, func=0x4bd8d0 <top_level_1>,
     arg=7407617) at /tmp.builds/emacs-23.0.60/src/eval.c:1230
#28 0x004be2f0 in command_loop ()
     at /tmp.builds/emacs-23.0.60/src/keyboard.c:1346
#29 0x004be67b in recursive_edit_1 ()
     at /tmp.builds/emacs-23.0.60/src/keyboard.c:962
#30 0x004be7b1 in Frecursive_edit ()
     at /tmp.builds/emacs-23.0.60/src/keyboard.c:1024
#31 0x004b43a5 in main (argc=2, argv=0x737300)
     at /tmp.builds/emacs-23.0.60/src/emacs.c:1784
(gdb)





  reply	other threads:[~2008-04-10  8:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09 21:37 Problems with Emacs (Cygwin) Angelo Graziosi
2008-04-10  1:32 ` Stefan Monnier
2008-04-10  8:10   ` Angelo Graziosi [this message]
2008-04-10  8:33   ` Angelo Graziosi
2008-04-10 23:46   ` Recent Emacs crashes when started in console Angelo Graziosi

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=47FDCB5C.6090008@alice.it \
    --to=angelo.graziosi@alice.it \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).