* 23.0.60; Crash after emacsclient -n foo.txt
@ 2008-02-02 16:30 Reiner Steib
2008-02-02 17:13 ` Juanma Barranquero
2008-02-02 17:58 ` Dan Nicolaescu
0 siblings, 2 replies; 6+ messages in thread
From: Reiner Steib @ 2008-02-02 16:30 UTC (permalink / raw)
To: emacs-devel
M-x report-emacs-bug RET wrote:
> Please describe exactly what actions triggered the bug
> and the precise symptoms of the bug:
After `M-x server-start RET' and running `emacsclient' from an xterm,
Emacs crashed:
In directory `/some/long/directory/xyz_01', I ran
emacsclient -n Kkkkk-Aaaaaaaaa-Hhhhh.txt &
[Directory and filenames modified for privacy reasons. They only
contain [-_A-z0-9], only innocent ASCII characters.]
The emacsclient binary belongs to Emacs 22.1, not to the CVS trunk as
the running emacs server instance.
> If Emacs crashed, and you have the Emacs process in the gdb debugger,
> please include the output from the following gdb commands:
> `bt full' and `xbacktrace'.
> If you would like to further debug the crash, please read the file
> /import/xtra/emacs/HEAD/share/emacs/23.0.60/etc/DEBUG for instructions.
--8<---------------cut here---------------start------------->8---
(gdb) run --eval '(gnus)'
Starting program: [...]/cvs-HEAD/i686/src/emacs --eval '(gnus)'
Failed to read a valid object file image from memory.
[Thread debugging using libthread_db enabled]
[New Thread -1219914048 (LWP 27596)]
Program received signal SIGPIPE, Broken pipe.
[Switching to Thread -1219914048 (LWP 27596)]
0xb7f56410 in ?? ()
(gdb) bt
#0 0xb7f56410 in ?? ()
#1 0xbfb9de48 in ?? ()
#2 0x00000074 in ?? ()
#3 0x09f24b94 in ?? ()
#4 0xb77def83 in __write_nocancel () from /lib/libpthread.so.0
#5 0x081632cf in emacs_write (fildes=9,
buf=0x9f24b94 "-error Unknown&_command:&_/some/long/directory/xyz_01/Kkkkk&-Aaaaaaaaa&-Hhhhh.txt", nbyte=116)
at [...]/cvs-HEAD/emacs/src/sysdep.c:3403
#6 0x08217600 in send_process (proc=173953540,
buf=0x9f24b94 "-error Unknown&_command:&_/some/long/directory/xyz_01/Kkkkk&-Aaaaaaaaa&-Hhhhh.txt", len=116,
object=156652923)
at [...]/cvs-HEAD/emacs/src/process.c:5576
#7 0x08217a99 in Fprocess_send_string (process=173953540, string=156652923)
at [...]/cvs-HEAD/emacs/src/process.c:5730
#8 0x081d2f15 in Ffuncall (nargs=3, args=0xbfb9dfc0)
at [...]/cvs-HEAD/emacs/src/eval.c:3028
#9 0x0820bf9b in Fbyte_code (bytestr=156368827, vector=159138980, maxdepth=24)
at [...]/cvs-HEAD/emacs/src/bytecode.c:679
#10 0x081d36c1 in funcall_lambda (fun=167175276, nargs=2,
arg_vector=0xbfb9e2c4)
at [...]/cvs-HEAD/emacs/src/eval.c:3212
#11 0x081d317d in Ffuncall (nargs=3, args=0xbfb9e2c0)
at [...]/cvs-HEAD/emacs/src/eval.c:3071
#12 0x0820bf9b in Fbyte_code (bytestr=156404355, vector=172015940, maxdepth=48)
at [...]/cvs-HEAD/emacs/src/bytecode.c:679
#13 0x081d20c1 in Feval (form=174297989)
at [...]/cvs-HEAD/emacs/src/eval.c:2362
#14 0x081d095e in internal_lisp_condition_case (var=138193097,
bodyform=174297989, handlers=174305133)
at [...]/cvs-HEAD/emacs/src/eval.c:1439
#15 0x0820cc46 in Fbyte_code (bytestr=156404435, vector=158817780, maxdepth=24)
at [...]/cvs-HEAD/emacs/src/bytecode.c:869
#16 0x081d36c1 in funcall_lambda (fun=157505748, nargs=2,
arg_vector=0xbfb9e970)
at [...]/cvs-HEAD/emacs/src/eval.c:3212
#17 0x081d339a in apply_lambda (fun=157505748, args=174297941, eval_flag=1)
at [...]/cvs-HEAD/emacs/src/eval.c:3136
#18 0x081d22ab in Feval (form=174297933)
at [...]/cvs-HEAD/emacs/src/eval.c:2398
#19 0x081cf102 in Fprogn (args=174297957)
at [...]/cvs-HEAD/emacs/src/eval.c:451
#20 0x081d08e7 in internal_lisp_condition_case (var=138635641,
bodyform=174304933, handlers=174297965)
at [...]/cvs-HEAD/emacs/src/eval.c:1422
#21 0x0820cc46 in Fbyte_code (bytestr=156398659, vector=159026708, maxdepth=48)
at [...]/cvs-HEAD/emacs/src/bytecode.c:869
#22 0x081d20c1 in Feval (form=174305173)
at [...]/cvs-HEAD/emacs/src/eval.c:2362
#23 0x081d0540 in internal_catch (tag=161469233, func=0x81d1c0f <Feval>,
arg=174305173)
at [...]/cvs-HEAD/emacs/src/eval.c:1230
#24 0x0820cbaf in Fbyte_code (bytestr=156398707, vector=172003628, maxdepth=16)
at [...]/cvs-HEAD/emacs/src/bytecode.c:854
#25 0x081d36c1 in funcall_lambda (fun=159460268, nargs=2,
arg_vector=0xbfb9f324)
at [...]/cvs-HEAD/emacs/src/eval.c:3212
#26 0x081d317d in Ffuncall (nargs=3, args=0xbfb9f320)
at [...]/cvs-HEAD/emacs/src/eval.c:3071
#27 0x081d26be in Fapply (nargs=2, args=0xbfb9f3c0)
at [...]/cvs-HEAD/emacs/src/eval.c:2513
#28 0x081d2a79 in apply1 (fn=172495753, arg=174821789)
at [...]/cvs-HEAD/emacs/src/eval.c:2777
#29 0x08216244 in read_process_output_call (fun_and_args=174821781)
at [...]/cvs-HEAD/emacs/src/process.c:4974
#30 0x081d0bb0 in internal_condition_case_1 (
bfun=0x8216221 <read_process_output_call>, arg=174821781,
handlers=138237329, hfun=0x8216246 <read_process_output_error_handler>)
at [...]/cvs-HEAD/emacs/src/eval.c:1542
#31 0x082168a9 in read_process_output (proc=173953540, channel=9)
at [...]/cvs-HEAD/emacs/src/process.c:5200
#32 0x08215e18 in wait_reading_process_output (time_limit=30, microsecs=0,
read_kbd=-1, do_display=1, wait_for_cell=138193097, wait_proc=0x0,
just_wait_proc=0)
at [...]/cvs-HEAD/emacs/src/process.c:4808
#33 0x0805eb84 in sit_for (timeout=240, reading=1, do_display=1)
at [...]/cvs-HEAD/emacs/src/dispnew.c:6608
#34 0x08148fe9 in read_char (commandflag=1, nmaps=5, maps=0xbfba0ba0,
---Type <return> to continue, or q <return> to quit---
prev_event=138193097, used_mouse_menu=0xbfba0d38, end_time=0x0)
at [...]/cvs-HEAD/emacs/src/keyboard.c:2969
#35 0x081536bb in read_key_sequence (keybuf=0xbfba0f48, bufsize=30,
prompt=138193097, dont_downcase_last=0, can_return_switch_frame=1,
fix_current_buffer=1)
at [...]/cvs-HEAD/emacs/src/keyboard.c:9460
#36 0x08145c4e in command_loop_1 ()
at [...]/cvs-HEAD/emacs/src/keyboard.c:1655
#37 0x081d0a84 in internal_condition_case (bfun=0x8145901 <command_loop_1>,
handlers=138237329, hfun=0x81452c1 <cmd_error>)
at [...]/cvs-HEAD/emacs/src/eval.c:1494
#38 0x0814565a in command_loop_2 ()
at [...]/cvs-HEAD/emacs/src/keyboard.c:1370
#39 0x081d0540 in internal_catch (tag=138232177,
func=0x8145637 <command_loop_2>, arg=138193097)
at [...]/cvs-HEAD/emacs/src/eval.c:1230
#40 0x08145610 in command_loop ()
at [...]/cvs-HEAD/emacs/src/keyboard.c:1349
#41 0x08144ece in recursive_edit_1 ()
at [...]/cvs-HEAD/emacs/src/keyboard.c:958
#42 0x0814503c in Frecursive_edit ()
at [...]/cvs-HEAD/emacs/src/keyboard.c:1020
#43 0x081438d1 in main (argc=3, argv=0xbfba1724)
at [...]/cvs-HEAD/emacs/src/emacs.c:1793
Lisp Backtrace:
"process-send-string" (0xbfb9dfc4)
"server-send-string" (0xbfb9e2c4)
"byte-code" (0xbfb9e550)
"server-return-error" (0xbfb9e970)
"byte-code" (0xbfb9eea0)
"server-process-filter" (0xbfb9f324)
--8<---------------cut here---------------end--------------->8---
> In GNU Emacs 23.0.60.2 (i686-pc-linux-gnu, GTK+ Version 2.10.6)
> of 2008-02-02 on viandante
> Windowing system distributor `The X.Org Foundation', version 11.0.70199902
> configured using `configure '--prefix=/import/xtra/emacs/HEAD'
> '--with-gtk' '--exec-prefix=/import/xtra/emacs/HEAD-i686'
> 'CFLAGS=-Wno-pointer-sign -O0 -fno-crossjumping -gdwarf-2 -g3''
[CVS trunk after unicode merge, fetched and built approx. 2008-02-02 12:47 CET]
> Important settings:
> value of $LC_ALL: nil
> value of $LC_COLLATE: nil
> value of $LC_CTYPE: nil
> value of $LC_MESSAGES: nil
> value of $LC_MONETARY: nil
> value of $LC_NUMERIC: nil
> value of $LC_TIME: nil
> value of $LANG: en_US.UTF-8
> value of $XMODIFIERS: @im=local
> locale-coding-system: utf-8-unix
> default-enable-multibyte-characters: t
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 23.0.60; Crash after emacsclient -n foo.txt
2008-02-02 16:30 23.0.60; Crash after emacsclient -n foo.txt Reiner Steib
@ 2008-02-02 17:13 ` Juanma Barranquero
2008-02-02 17:33 ` Reiner Steib
2008-02-02 17:58 ` Dan Nicolaescu
1 sibling, 1 reply; 6+ messages in thread
From: Juanma Barranquero @ 2008-02-02 17:13 UTC (permalink / raw)
To: Reiner Steib, emacs-devel
On Feb 2, 2008 5:30 PM, Reiner Steib <reinersteib+gmane@imap.cc> wrote:
> The emacsclient binary belongs to Emacs 22.1, not to the CVS trunk as
> the running emacs server instance.
AFAIK, emacsclient/server from 22.X and the trunk are not
interoperable right now. Aside of the multi-tty stuff, the trunk's
emacsclient sends args differently.
I think we should fix the trunk's server.el to accept 22.X
emacsclient's requests.
Juanma
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 23.0.60; Crash after emacsclient -n foo.txt
2008-02-02 17:13 ` Juanma Barranquero
@ 2008-02-02 17:33 ` Reiner Steib
0 siblings, 0 replies; 6+ messages in thread
From: Reiner Steib @ 2008-02-02 17:33 UTC (permalink / raw)
To: Juanma Barranquero; +Cc: emacs-devel
On Sat, Feb 02 2008, Juanma Barranquero wrote:
> On Feb 2, 2008 5:30 PM, Reiner Steib <reinersteib+gmane@imap.cc> wrote:
>> The emacsclient binary belongs to Emacs 22.1, not to the CVS trunk as
>> the running emacs server instance.
>
> AFAIK, emacsclient/server from 22.X and the trunk are not
> interoperable right now. Aside of the multi-tty stuff, the trunk's
> emacsclient sends args differently.
>
> I think we should fix the trunk's server.el to accept 22.X
> emacsclient's requests.
Yes. Emacs shouldn't crash, at least.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 23.0.60; Crash after emacsclient -n foo.txt
2008-02-02 16:30 23.0.60; Crash after emacsclient -n foo.txt Reiner Steib
2008-02-02 17:13 ` Juanma Barranquero
@ 2008-02-02 17:58 ` Dan Nicolaescu
2008-02-02 18:24 ` Reiner Steib
1 sibling, 1 reply; 6+ messages in thread
From: Dan Nicolaescu @ 2008-02-02 17:58 UTC (permalink / raw)
To: emacs-devel
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> M-x report-emacs-bug RET wrote:
>
> > Please describe exactly what actions triggered the bug
> > and the precise symptoms of the bug:
>
> After `M-x server-start RET' and running `emacsclient' from an xterm,
> Emacs crashed:
>
> In directory `/some/long/directory/xyz_01', I ran
> emacsclient -n Kkkkk-Aaaaaaaaa-Hhhhh.txt &
>
> [Directory and filenames modified for privacy reasons. They only
> contain [-_A-z0-9], only innocent ASCII characters.]
>
> The emacsclient binary belongs to Emacs 22.1, not to the CVS trunk as
> the running emacs server instance.
This works fine for me. But instead of:
> > In GNU Emacs 23.0.60.2 (i686-pc-linux-gnu, GTK+ Version 2.10.6)
I have:
GNU Emacs 23.0.60.1 (i686-pc-linux-gnu, GTK+ Version 2.12.3))
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 23.0.60; Crash after emacsclient -n foo.txt
2008-02-02 17:58 ` Dan Nicolaescu
@ 2008-02-02 18:24 ` Reiner Steib
2008-02-02 18:54 ` Dan Nicolaescu
0 siblings, 1 reply; 6+ messages in thread
From: Reiner Steib @ 2008-02-02 18:24 UTC (permalink / raw)
To: Dan Nicolaescu; +Cc: emacs-devel
On Sat, Feb 02 2008, Dan Nicolaescu wrote:
> Reiner Steib <reinersteib+gmane@imap.cc> writes:
> > M-x report-emacs-bug RET wrote:
> >
> > > Please describe exactly what actions triggered the bug
> > > and the precise symptoms of the bug:
> >
> > After `M-x server-start RET' and running `emacsclient' from an xterm,
> > Emacs crashed:
[...]
> > The emacsclient binary belongs to Emacs 22.1, not to the CVS trunk as
> > the running emacs server instance.
>
> This works fine for me. But instead of:
>
> > > In GNU Emacs 23.0.60.2 (i686-pc-linux-gnu, GTK+ Version 2.10.6)
>
> I have:
> GNU Emacs 23.0.60.1 (i686-pc-linux-gnu, GTK+ Version 2.12.3))
I can't reproduce the crash (I still have in a screen session,
though), but I get an error from emacsclient:
| [...]/cvs-HEAD/emacs$ [...]/cvs-HEAD/i686/src/emacs -Q
|
| [1]+ Stopped [...]/cvs-HEAD/i686/src/emacs -Q
| [...]/cvs-HEAD/emacs$ bg
| [1]+ [...]/cvs-HEAD/i686/src/emacs -Q &
|
| [`M-x server-start RET' in Emacs]
|
| [...]/cvs-HEAD/emacs$ /usr/bin/emacsclient vpath.sed
| Waiting for Emacs...
| -error Unknown&_command:&_[...]/cvs&-HEAD/emacs/vpath.sed
When adding `-n', I get no error, but the file isn't opened in the
emacs server session. (I don't think that the client tries to talk to
the crashed server, since the socket's timestamp is new. IIRC, `M-x
server-start RET' overrides previous sessions.)
| [...]/cvs-HEAD/emacs$ /usr/bin/emacsclient -n vpath.sed
| [...]/cvs-HEAD/emacs$
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 23.0.60; Crash after emacsclient -n foo.txt
2008-02-02 18:24 ` Reiner Steib
@ 2008-02-02 18:54 ` Dan Nicolaescu
0 siblings, 0 replies; 6+ messages in thread
From: Dan Nicolaescu @ 2008-02-02 18:54 UTC (permalink / raw)
To: emacs-devel
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Sat, Feb 02 2008, Dan Nicolaescu wrote:
>
> > Reiner Steib <reinersteib+gmane@imap.cc> writes:
> > > M-x report-emacs-bug RET wrote:
> > >
> > > > Please describe exactly what actions triggered the bug
> > > > and the precise symptoms of the bug:
> > >
> > > After `M-x server-start RET' and running `emacsclient' from an xterm,
> > > Emacs crashed:
> [...]
> > > The emacsclient binary belongs to Emacs 22.1, not to the CVS trunk as
> > > the running emacs server instance.
> >
> > This works fine for me. But instead of:
> >
> > > > In GNU Emacs 23.0.60.2 (i686-pc-linux-gnu, GTK+ Version 2.10.6)
> >
> > I have:
> > GNU Emacs 23.0.60.1 (i686-pc-linux-gnu, GTK+ Version 2.12.3))
>
> I can't reproduce the crash (I still have in a screen session,
> though), but I get an error from emacsclient:
>
> | [...]/cvs-HEAD/emacs$ [...]/cvs-HEAD/i686/src/emacs -Q
> |
> | [1]+ Stopped [...]/cvs-HEAD/i686/src/emacs -Q
> | [...]/cvs-HEAD/emacs$ bg
> | [1]+ [...]/cvs-HEAD/i686/src/emacs -Q &
> |
> | [`M-x server-start RET' in Emacs]
> |
> | [...]/cvs-HEAD/emacs$ /usr/bin/emacsclient vpath.sed
> | Waiting for Emacs...
> | -error Unknown&_command:&_[...]/cvs&-HEAD/emacs/vpath.sed
>
> When adding `-n', I get no error, but the file isn't opened in the
> emacs server session. (I don't think that the client tries to talk to
> the crashed server, since the socket's timestamp is new. IIRC, `M-x
> server-start RET' overrides previous sessions.)
That's better given that you don't see any crash. After the multi-tty
merge emacsclient used to refuse to connect to a different server
version. It doesn't seem to do it anymore. But IMHO there are more
interesting issues to solve than this.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2008-02-02 18:54 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-02-02 16:30 23.0.60; Crash after emacsclient -n foo.txt Reiner Steib
2008-02-02 17:13 ` Juanma Barranquero
2008-02-02 17:33 ` Reiner Steib
2008-02-02 17:58 ` Dan Nicolaescu
2008-02-02 18:24 ` Reiner Steib
2008-02-02 18:54 ` Dan Nicolaescu
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).