Unfortunately, that stack trace doesn't have any useful information, so we'll
need a stack trace with debugging symbols.  We'll wait to hear back from you.

Hi,

It just happened again. This extra information can I provide: 

* top (focused) gnome-terminal had vim open. I'll cross reference bug #148659
* In vim I selected accidently (touchpad at laptop) a complete screen
* My windowmanager is sawfish

Status about the 'unstripped executable': just compiled & installed.

Had a crash again.
Bugbuddy produced this:

Debugging Information:

Backtrace was generated from '/usr/bin/gnome-terminal'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 17712)]
[New Thread 32769 (LWP 17739)]
[New Thread 16386 (LWP 17742)]
0x0ea7e110 in waitpid () from /lib/libpthread.so.0

+ Trace 56489

That is the same as in the bugreport opening,
but now without "(no debugging symbols found)"

It was again with vim in the top screen.

Changed status from NEEDINFO to OPEN
as I don't known who to provide more information
now the unstripped version didn't reveal any more.

What compiling flags did you use?

-O2

To be more precise:

CFLAGS =  -I/usr/X11R6/include -DXTHREADS -DORBIT2=1 -pthread
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/X11R6/include
-I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/freetype2
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gconf/2
-I/usr/include/orbit-2.0 -I/usr/include/libglade-2.0 -I/usr/include/libxml2
-I/usr/include/libgnomeui-2.0 -I/usr/include/libgnome-2.0
-I/usr/include/libgnomecanvas-2.0 -I/usr/include/libart-2.0
-I/usr/include/libbonoboui-2.0 -I/usr/include/libbonobo-2.0
-I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include
-I/usr/include/bonobo-activation-2.0 -I/usr/include/startup-notification-1.0  
-g -Wall -O2

does it miss a  "compile for debugging"  flag?

No, that looks fine.  Did you recompile glib and gtk+ too or just gnome-terminal?

only gnome-terminal was recompiled.
(I'm not sure if it survived an apt-get update )

I just got:


Backtrace was generated from '/usr/bin/gnome-terminal'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 3259)]
[New Thread 32769 (LWP 3277)]
[New Thread 16386 (LWP 3278)]
0x0ea5d110 in waitpid () from /lib/libpthread.so.0

+ Trace 59484

so no real progress :-(

today also

Backtrace was generated from '/usr/bin/gnome-terminal'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 3259)]
[New Thread 32769 (LWP 3277)]
[New Thread 16386 (LWP 3278)]
0x0ea5d110 in waitpid () from /lib/libpthread.so.0

+ Trace 60054

It seems to me that some rare mouse movement causes this crash.
The touchpad on the laptop accetendly selects a block
the windows has to be updated, but gnome-terminal crashes at that point.

still hard to reproduce, but it happened again.

some "block select" by the touchpad mouse and a crash ...

see also bug 169193

just again.

Hi Geert,

thanks a lot for being persistent about this, I hope we can squash this issue..
any chance you could compile vte with --enable-debugging and post "bt full" from 
gdb, next time you stumble into this?

Yes, I think I can compile vte with --enable-debugging.

But what is vte the acronym for? (What is the (full) name of source?)

Something else:

I have about 12 terminal sessions open,
with `ps -ef` I see only three processes.

I would expect 12 proces or one single process

The tarball is named vte. Gnome-terminal --disable-factory starts a new process,
perhaps you used that?

$ ps -ef | grep terminal | cut -c -79
stappers  3485     1  0 20:14 ?        00:00:20 gnome-terminal --sm-config-pref
stappers  3498  3485  0 20:14 ?        00:00:00 gnome-terminal --sm-config-pref
stappers  3499  3498  0 20:14 ?        00:00:00 gnome-terminal --sm-config-pref
$ ps -ef | grep terminal | grep 3499
stappers  3499  3498  0 20:14 ?        00:00:00 gnome-terminal
--sm-config-prefix /gnome-terminal-Am7DHU/ --sm-client-id
11ac180019000108866086300000004300006 --screen 0
--window-with-profile-internal-id=Default --show-menubar
--role=gnome-terminal-534--866041725-1088660865 --active --geometry 80x24
--title mir-CHROOT --working-directory /home/stappers --zoom 1
--window-with-profile-internal-id=Default --show-menubar
--role=gnome-terminal-534-633337202-1088661043 --active --geometry 123x24
--title Mutt --working-directory /home/stappers --zoom 1
--window-with-profile-internal-id=Default --show-menubar
--role=gnome-terminal-534--758863760-1088661091 --active --geometry 80x24
--title conglomerate --working-directory /usr/src/conglomerate --zoom 1
--window-with-profile-internal-id=Default --show-menubar
--role=gnome-terminal-534--283225869-1088661153 --active --geometry 80x24
--title root@bahrain --working-directory /home/stappers --zoom 1
--window-with-profile-internal-id=Default --show-menubar
--role=gnome-terminal-534-1595522225-1088661277 --active --geometry 80x24
--title mitchit --working-directory /usr/src/mitch --zoom 1
--window-with-profile-internal-id=Default --show-menubar
--role=gnome-terminal-1123--978817830-1088675750 --active --geometry 80x40
--title IRC --working-directory /home/stappers --zoom 1
--window-with-profile-internal-id=Default --show-menubar
--role=gnome-terminal-5206-1610116594-1107079645 --active --geometry 80x24
--title cadiz --working-directory /home/stappers --zoom 1
--window-with-profile-internal-id=Default --show-menubar
--role=gnome-terminal-17497-581156881-1110032036 --active --geometry 121x24
--title cadiz-wide --working-directory /home/stappers --zoom 1
$ ps -ef | grep terminal | grep 3499 | wc
      1     110    1716

Installed today gnome-terminal version 2.10
(I shall update when new information is available)

Hi Geert,

thanks a lot for following up. Did you also update vte to the latest release
0.11.13?
(you can find it here: http://ftp.gnome.org/pub/GNOME/sources/vte/0.11/
If you could compile it adding '--enable-debugging' to your ./configure
switch, that'd be perfect to get a good stack trace

Hello,

Over here are packages used. I (have the unfounded) fear for dependency hell.
So I had a look at package build system, but there is too much magic done.

I shall contact the packager for assistence.

Got the information:

* modify the configure and configure.in scripts to get --enable-debugging

* build the package with DEB_BUILD_OPTIONS=nostrip


(no actual rebuild done yet, just parking the information here)

had the first crash last thursday and today a new reminder
to build the debug version for more information.

Sorry we can't really help you without a good backtrace. There's a new release
of vte (the terminal emulator widget) out since we last asked you to recompile
which fixes a few crashes, not sure they are related to this, but we still need
to get a backtrace to be able to track this down...

(Four weeks went fine, today a crash.)

I understand that it is up to me to provide more information,
but I still fear the rebuild and mostly the install of modified libraries.

To be continued.

november 23, had three crashes sinces last "check in"

still now debug versions installed.
(and still other priorities ( hey, what is new ;-) )

I just got another reminder ...

Closing this bug report as no further information has been provided. Geert, please feel free to reopen this bug if you can provide the information asked for.
Thanks!