unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Problems with gtk-build / emacs-22.1.1
@ 2007-09-09 20:31 Dieter Jurzitza
  2007-09-10  6:20 ` Jan Djärv
  0 siblings, 1 reply; 4+ messages in thread
From: Dieter Jurzitza @ 2007-09-09 20:31 UTC (permalink / raw)
  To: emacs-devel

Dear listmembers,
I recently built a new emacs on my system:
This is GNU Emacs 22.1.1 (i586-suse-linux-gnu, GTK+ Version 2.6.4) 

I am using kde (suse 9.3) and mainly start emacs iconic at startup and use 
gnuclient to edit files whenever apropriate.

With the new emacs I am facing the problem that, after fresh login, the first 
call to 
gnuclient <myfile> & 
causes emacs to crash. In contrast, when I restart emacs using
emacs --iconic &
all subsequent calls
gnuclient <myfile> &
work flawlessly.
I then decided to start emacs within a script doing
strace /usr/bin/emacs --iconic > logfile 2>&1 &
Thereby I can trace the crash and see a SIGSEGV / Gdk error:


****************** EXCERPTEXCERPT ********************************************

--- SIGIO (I/O possible) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
read(4, "\1\30W\7\0\0\0\0w\0\0\0\0\0\0\0\340\20\34\0\0\0\0\0H\273"..., 32) = 
32
write(4, "6\30\2\0\263\1\300\0016\0\2\0\262\1\300\0015\30\4\0\267"..., 340) = 
340
--- SIGIO (I/O possible) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
read(4, "\1\30f\7\0\0\0\0w\0\0\0\0\0\0\0\240\5\4\0\0\0\0\0H\273"..., 32) = 32
write(4, "6\30\2\0\267\1\300\0015\30\4\0\272\1\300\1w\0\0\0\n\0\4"..., 60) = 
60
--- SIGIO (I/O possible) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
read(4, "\1\30j\7\0\0\0\0w\0\0\0\0\0\0\0\n\0\4\0\0\0\0\0H\273\244"..., 32) = 
32
write(4, "6\30\2\0\272\1\300\0015\30\4\0\273\1\300\1w\0\0\0\302\20"..., 144) = 
144
--- SIGIO (I/O possible) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
read(4, "\1\30r\7\0\0\0\0w\0\0\0\0\0\0\0\302\20\4\0\0\0\0\0H\273"..., 32) = 32
write(8, "\2\0\4\0x\0\240\0\10\0\0\0\0\0\0\0*\2\3\0h\0\240\0\367"..., 1424) = 
1424
write(4, "6\30\2\0\274\1\300\0016\30\2\0\273\1\300\1", 16) = 16
write(8, "+\0\1\0", 4)                  = 4
read(8, 0xbfffa0b0, 32)                 = -1 EAGAIN (Resource temporarily 
unavailable)
select(9, [8], NULL, NULL, NULL)        = 1 (in [8])
--- SIGIO (I/O possible) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
read(8, "\n\5\233\3x\0\240\0\0\365\377\277\350@v\10\10\0\0\0H\206"..., 32) = 
32
read(8, "\n\2\233\3g\0\240\0\0\365\377\277W\270\f\10\5\0\0\0H\206"..., 32) = 
32
read(8, "\t\0\233\3h\0\240\0\0\365\377\2771\275\f\10\220m\271\10"..., 32) = 32
read(8, "\1\2\234\3\0\0\0\0h\0\240\0\0\0\0\0\0\0\0\0\10\0\0\0\20"..., 32) = 32
read(8, "\0\t\243\3\262\1\300\1\0\0>\0\0\0\0\0\0\0\0\0\10\0\0\0"..., 32) = 32
open("/usr/X11R6/lib/X11/XErrorDB", O_RDONLY) = 12
fstat64(12, {st_mode=S_IFREG|0444, st_size=36378, ...}) = 0
read(12, "! $Xorg: XErrorDB,v 1.3 2000/08/"..., 36378) = 36378
close(12)                               = 0
brk(0x8ae9000)                          = 0x8ae9000
brk(0x8af2000)                          = 0x8af2000
brk(0x8afa000)                          = 0x8afa000
brk(0x8afb000)                          = 0x8afb000
brk(0x8afc000)                          = 0x8afc000
brk(0x8afd000)                          = 0x8afd000
brk(0x8afe000)                          = 0x8afe000
write(8, "+\0\1\0", 4)                  = 4
--- SIGIO (I/O possible) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
read(8, "\0\t\317\3\267\1\300\1\0\0>\0\0\0\0\0\0\0\0\0\10\0\0\0"..., 32) = 32
write(8, "+\0\1\0", 4)                  = 4
--- SIGIO (I/O possible) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
read(8, "\0\t\320\3\272\1\300\1\0\0>\0\0\0\0\0\0\0\0\0\10\0\0\0"..., 32) = 32
write(8, "+\0\1\0", 4)                  = 4
--- SIGIO (I/O possible) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
read(8, "\1\2\336\3\0\0\0\0h\0\240\0\0\0\0\0\1\0\0\0\10\0\0\0\20"..., 32) = 32
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
rt_sigaction(SIGSEGV, {SIG_DFL}, {0x80f63b0, [], SA_RESTART}, 8) = 0
select(8, [7], NULL, NULL, {0, 0})      = 0 (Timeout)
select(8, [7], NULL, NULL, {0, 0})      = 0 (Timeout)
ioctl(4, FIONREAD, [0])                 = 0
poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN, revents=POLLIN}], 2, 0) = 1
ioctl(4, FIONREAD, [0])                 = 0
poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN, revents=POLLIN}], 2, 0) = 1
write(8, "\24\0\6\0g\0\240\0\370\0\0\0\4\0\0\0\0\0\0\0\377\377\377"..., 24) = 
24
--- SIGIO (I/O possible) @ 0 (0) ---
sigreturn()                             = ? (mask now [SEGV])
read(8, "\1\2\337\3\0\0\0\0h\0\240\0\0\0\0\0\1\0\0\0\10\0\0\0\20"..., 32) = 32
write(2, "\nGdk-ERROR **: file gdkevents-x1"..., 109
Gdk-ERROR **: file gdkevents-x11.c: line 581 (set_screen_from_root): assertion 
failed: (screen)
aborting...
) = 109
kill(7193, SIGABRT)                     = 0
--- SIGABRT (Aborted) @ 0 (0) ---
rt_sigaction(SIGABRT, {SIG_DFL}, {0x80f63b0, [], SA_RESTART}, 8) = 0
select(8, [7], NULL, NULL, {0, 0})      = 0 (Timeout)
select(8, [7], NULL, NULL, {0, 0})      = 0 (Timeout)
ioctl(4, FIONREAD, [0])                 = 0
poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN, revents=POLLIN}], 2, 0) = 1
ioctl(4, FIONREAD, [0])                 = 0
poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN, revents=POLLIN}], 2, 0) = 1
write(2, "\n", 1
)                       = 1
write(2, "(process:", 9(process:)                = 9
write(2, "7193", 47193)                     = 4
write(2, "): ", 3): )                      = 3
write(2, "Gdk", 3Gdk)                      = 3
write(2, "-", 1-)                        = 1
write(2, "ERROR (recursed) **", 19ERROR (recursed) **)     = 19
write(2, ": ", 2: )                       = 2
write(2, "file gdkevents-x11.c: line 581 ("..., 81file gdkevents-x11.c: line 
581 (set_screen_from_root): assertion failed: (screen)) = 81
write(2, "\naborting...\n", 13
****************** EXCERPTEXCERPT ********************************************

But I personally have no clue what to do about and whether this can be fixed 
with finite effort.

In order to not flood the list I just send this part of the log, not knowing 
whether or not the important information can be found within. If someone 
would be interested to take a look into the entire log, please give me a note 
- I could send the log to someone personally.

Anyway, many thanks for your help in advance, many thanks for working on emacs 
anyway :-))

Take care



Dieter Jurzitza

-- 
-----------------------------------------------------------

                               |
                                \
                 /\_/\           |
                | ~x~ |/-----\   /
                 \   /-       \_/
  ^^__   _        /  _  ____   /
 <°°__ \- \_/     |  |/    |  |
  ||  ||         _| _|    _| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
-----------------------------------------------------------

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Problems with gtk-build / emacs-22.1.1
  2007-09-09 20:31 Problems with gtk-build / emacs-22.1.1 Dieter Jurzitza
@ 2007-09-10  6:20 ` Jan Djärv
  2007-09-10 19:38   ` Dieter Jurzitza
  2007-09-10 19:50   ` Dieter Jurzitza
  0 siblings, 2 replies; 4+ messages in thread
From: Jan Djärv @ 2007-09-10  6:20 UTC (permalink / raw)
  To: Dieter Jurzitza; +Cc: emacs-devel



Dieter Jurzitza skrev:
> Dear listmembers,
> I recently built a new emacs on my system:
> This is GNU Emacs 22.1.1 (i586-suse-linux-gnu, GTK+ Version 2.6.4) 
> 
> I am using kde (suse 9.3) and mainly start emacs iconic at startup and use 
> gnuclient to edit files whenever apropriate.
> 
> With the new emacs I am facing the problem that, after fresh login, the first 
> call to 
> gnuclient <myfile> & 
> causes emacs to crash. In contrast, when I restart emacs using
> emacs --iconic &
> all subsequent calls
> gnuclient <myfile> &
> work flawlessly.
> I then decided to start emacs within a script doing
> strace /usr/bin/emacs --iconic > logfile 2>&1 &
> Thereby I can trace the crash and see a SIGSEGV / Gdk error:

Strace is not really useful.  Start emacs in gdb instead and see where it 
crashes.  Also, there must have been some output on stderr, what was it?

	Jan D.

> 
> 
> ****************** EXCERPTEXCERPT ********************************************
> 
> --- SIGIO (I/O possible) @ 0 (0) ---
> sigreturn()                             = ? (mask now [])
> read(4, "\1\30W\7\0\0\0\0w\0\0\0\0\0\0\0\340\20\34\0\0\0\0\0H\273"..., 32) = 
> 32
> write(4, "6\30\2\0\263\1\300\0016\0\2\0\262\1\300\0015\30\4\0\267"..., 340) = 
> 340
> --- SIGIO (I/O possible) @ 0 (0) ---
> sigreturn()                             = ? (mask now [])
> read(4, "\1\30f\7\0\0\0\0w\0\0\0\0\0\0\0\240\5\4\0\0\0\0\0H\273"..., 32) = 32
> write(4, "6\30\2\0\267\1\300\0015\30\4\0\272\1\300\1w\0\0\0\n\0\4"..., 60) = 
> 60
> --- SIGIO (I/O possible) @ 0 (0) ---
> sigreturn()                             = ? (mask now [])
> read(4, "\1\30j\7\0\0\0\0w\0\0\0\0\0\0\0\n\0\4\0\0\0\0\0H\273\244"..., 32) = 
> 32
> write(4, "6\30\2\0\272\1\300\0015\30\4\0\273\1\300\1w\0\0\0\302\20"..., 144) = 
> 144
> --- SIGIO (I/O possible) @ 0 (0) ---
> sigreturn()                             = ? (mask now [])
> read(4, "\1\30r\7\0\0\0\0w\0\0\0\0\0\0\0\302\20\4\0\0\0\0\0H\273"..., 32) = 32
> write(8, "\2\0\4\0x\0\240\0\10\0\0\0\0\0\0\0*\2\3\0h\0\240\0\367"..., 1424) = 
> 1424
> write(4, "6\30\2\0\274\1\300\0016\30\2\0\273\1\300\1", 16) = 16
> write(8, "+\0\1\0", 4)                  = 4
> read(8, 0xbfffa0b0, 32)                 = -1 EAGAIN (Resource temporarily 
> unavailable)
> select(9, [8], NULL, NULL, NULL)        = 1 (in [8])
> --- SIGIO (I/O possible) @ 0 (0) ---
> sigreturn()                             = ? (mask now [])
> read(8, "\n\5\233\3x\0\240\0\0\365\377\277\350@v\10\10\0\0\0H\206"..., 32) = 
> 32
> read(8, "\n\2\233\3g\0\240\0\0\365\377\277W\270\f\10\5\0\0\0H\206"..., 32) = 
> 32
> read(8, "\t\0\233\3h\0\240\0\0\365\377\2771\275\f\10\220m\271\10"..., 32) = 32
> read(8, "\1\2\234\3\0\0\0\0h\0\240\0\0\0\0\0\0\0\0\0\10\0\0\0\20"..., 32) = 32
> read(8, "\0\t\243\3\262\1\300\1\0\0>\0\0\0\0\0\0\0\0\0\10\0\0\0"..., 32) = 32
> open("/usr/X11R6/lib/X11/XErrorDB", O_RDONLY) = 12
> fstat64(12, {st_mode=S_IFREG|0444, st_size=36378, ...}) = 0
> read(12, "! $Xorg: XErrorDB,v 1.3 2000/08/"..., 36378) = 36378
> close(12)                               = 0
> brk(0x8ae9000)                          = 0x8ae9000
> brk(0x8af2000)                          = 0x8af2000
> brk(0x8afa000)                          = 0x8afa000
> brk(0x8afb000)                          = 0x8afb000
> brk(0x8afc000)                          = 0x8afc000
> brk(0x8afd000)                          = 0x8afd000
> brk(0x8afe000)                          = 0x8afe000
> write(8, "+\0\1\0", 4)                  = 4
> --- SIGIO (I/O possible) @ 0 (0) ---
> sigreturn()                             = ? (mask now [])
> read(8, "\0\t\317\3\267\1\300\1\0\0>\0\0\0\0\0\0\0\0\0\10\0\0\0"..., 32) = 32
> write(8, "+\0\1\0", 4)                  = 4
> --- SIGIO (I/O possible) @ 0 (0) ---
> sigreturn()                             = ? (mask now [])
> read(8, "\0\t\320\3\272\1\300\1\0\0>\0\0\0\0\0\0\0\0\0\10\0\0\0"..., 32) = 32
> write(8, "+\0\1\0", 4)                  = 4
> --- SIGIO (I/O possible) @ 0 (0) ---
> sigreturn()                             = ? (mask now [])
> read(8, "\1\2\336\3\0\0\0\0h\0\240\0\0\0\0\0\1\0\0\0\10\0\0\0\20"..., 32) = 32
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> rt_sigaction(SIGSEGV, {SIG_DFL}, {0x80f63b0, [], SA_RESTART}, 8) = 0
> select(8, [7], NULL, NULL, {0, 0})      = 0 (Timeout)
> select(8, [7], NULL, NULL, {0, 0})      = 0 (Timeout)
> ioctl(4, FIONREAD, [0])                 = 0
> poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN, revents=POLLIN}], 2, 0) = 1
> ioctl(4, FIONREAD, [0])                 = 0
> poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN, revents=POLLIN}], 2, 0) = 1
> write(8, "\24\0\6\0g\0\240\0\370\0\0\0\4\0\0\0\0\0\0\0\377\377\377"..., 24) = 
> 24
> --- SIGIO (I/O possible) @ 0 (0) ---
> sigreturn()                             = ? (mask now [SEGV])
> read(8, "\1\2\337\3\0\0\0\0h\0\240\0\0\0\0\0\1\0\0\0\10\0\0\0\20"..., 32) = 32
> write(2, "\nGdk-ERROR **: file gdkevents-x1"..., 109
> Gdk-ERROR **: file gdkevents-x11.c: line 581 (set_screen_from_root): assertion 
> failed: (screen)
> aborting...
> ) = 109
> kill(7193, SIGABRT)                     = 0
> --- SIGABRT (Aborted) @ 0 (0) ---
> rt_sigaction(SIGABRT, {SIG_DFL}, {0x80f63b0, [], SA_RESTART}, 8) = 0
> select(8, [7], NULL, NULL, {0, 0})      = 0 (Timeout)
> select(8, [7], NULL, NULL, {0, 0})      = 0 (Timeout)
> ioctl(4, FIONREAD, [0])                 = 0
> poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN, revents=POLLIN}], 2, 0) = 1
> ioctl(4, FIONREAD, [0])                 = 0
> poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN, revents=POLLIN}], 2, 0) = 1
> write(2, "\n", 1
> )                       = 1
> write(2, "(process:", 9(process:)                = 9
> write(2, "7193", 47193)                     = 4
> write(2, "): ", 3): )                      = 3
> write(2, "Gdk", 3Gdk)                      = 3
> write(2, "-", 1-)                        = 1
> write(2, "ERROR (recursed) **", 19ERROR (recursed) **)     = 19
> write(2, ": ", 2: )                       = 2
> write(2, "file gdkevents-x11.c: line 581 ("..., 81file gdkevents-x11.c: line 
> 581 (set_screen_from_root): assertion failed: (screen)) = 81
> write(2, "\naborting...\n", 13
> ****************** EXCERPTEXCERPT ********************************************
> 
> But I personally have no clue what to do about and whether this can be fixed 
> with finite effort.
> 
> In order to not flood the list I just send this part of the log, not knowing 
> whether or not the important information can be found within. If someone 
> would be interested to take a look into the entire log, please give me a note 
> - I could send the log to someone personally.
> 
> Anyway, many thanks for your help in advance, many thanks for working on emacs 
> anyway :-))
> 
> Take care
> 
> 
> 
> Dieter Jurzitza
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Problems with gtk-build / emacs-22.1.1
  2007-09-10  6:20 ` Jan Djärv
@ 2007-09-10 19:38   ` Dieter Jurzitza
  2007-09-10 19:50   ` Dieter Jurzitza
  1 sibling, 0 replies; 4+ messages in thread
From: Dieter Jurzitza @ 2007-09-10 19:38 UTC (permalink / raw)
  To: emacs-devel

Dear Jan,
dear listmembers,
thanks for looking into this. 
Am Montag, 10. September 2007 08:20 schrieb Jan Djärv:
> Dieter Jurzitza skrev:
> crashes.  Also, there must have been some output on stderr, what was it?
See commandline: 
>> I then decided to start emacs within a script doing
>> strace /usr/bin/emacs --iconic > logfile 2>&1 &

The output to stderr has been sent into the logfile. So, whatever has been 
printed to either stdout or stderr has been listed. I have been sending the 
part "around" the SIGSEGV because the logfile contains several hundred 
kilobytes.

I obeyed your suggestion and started emacs within a gdb-process. But the 
output is *very* small:

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 "i586-suse-linux"...Using host libthread_db library 
"/lib/tls/libthread_db.so.1".

[Thread debugging using libthread_db enabled]
[New Thread 1085123872 (LWP 16297)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1085123872 (LWP 16297)]
0x405e96f7 in XFreeGC () from /usr/X11R6/lib/libX11.so.6
(gdb)

But I do not have any clue what that could mean. Do you see anything here that 
could be debugged further? Please note that this happens *only* when starting 
emacs from within ~/.kde/Autostart  - if I start emacs in a xterm I do not 
see similar problems.

Any suggestions are highly appreciated!
Thanks again,
take care



Dieter

>
> 	Jan D.
*****
-- 
-----------------------------------------------------------

                               |
                                \
                 /\_/\           |
                | ~x~ |/-----\   /
                 \   /-       \_/
  ^^__   _        /  _  ____   /
 <°°__ \- \_/     |  |/    |  |
  ||  ||         _| _|    _| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
-----------------------------------------------------------

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Problems with gtk-build / emacs-22.1.1
  2007-09-10  6:20 ` Jan Djärv
  2007-09-10 19:38   ` Dieter Jurzitza
@ 2007-09-10 19:50   ` Dieter Jurzitza
  1 sibling, 0 replies; 4+ messages in thread
From: Dieter Jurzitza @ 2007-09-10 19:50 UTC (permalink / raw)
  To: emacs-devel

Dear listmembers,
I made (some ...) progress. If I start emacs like this (kde):

Alt-F2 # run program
emacs

or as readily said from within ~/.kde/Autostart/emacs :
(cat ~/.kde/Autostart/emacs)
#!/bin/sh
/usr/bin/emacs --iconic &

I can repetitively crash emacs by the first gnuclient <filename> call.

In contrast, if I start emacs from within ~/.kde/Autostart/emacs "through" a 
xterm :
(cat ~/.kde/Autostart/emacs)
#!/bin/sh
xterm -iconic -e "/usr/bin/emacs --iconic &"

it is working just fine, the call

gnuclient <filename>

does what it is expected to do: open file <filename> within an emacs buffer. 
So, I have a plaster for the problem but hardly understand what is going on.

If anyone has any further ideas on this ....

Thanks again,
take care



Dieter Jurzitza

-- 
-----------------------------------------------------------

                               |
                                \
                 /\_/\           |
                | ~x~ |/-----\   /
                 \   /-       \_/
  ^^__   _        /  _  ____   /
 <°°__ \- \_/     |  |/    |  |
  ||  ||         _| _|    _| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
-----------------------------------------------------------

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2007-09-10 19:50 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-09-09 20:31 Problems with gtk-build / emacs-22.1.1 Dieter Jurzitza
2007-09-10  6:20 ` Jan Djärv
2007-09-10 19:38   ` Dieter Jurzitza
2007-09-10 19:50   ` Dieter Jurzitza

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).