since i upgraded my whole system i experience segfaults with roxterm. i would
like to post a backtrace but i don't know which configure options should i use
during recompilation (configure --help is not really useful).

thank you, jose

Just make sure CFLAGS includes -g (I think it does by default). Instead of
installing roxterm you could run it in place with its AppRun script eg

./AppRun --debug

and run it in another terminal eg gnome-terminal or xterm. The --debug option
will run it in gdb. It would also help if you install debugging packages for
GTK etc if there are any for your distro, for example libglib2.0-0-dbg,
libgtk2.0-0-dbg in Debian and Ubuntu etc.

Valgrind may also help:

ulimit -c unlimited
./AppRun --valgrind

Please could you also tell me if there's a particular action that makes it
crash.

unfortunately i do not now how to reproduce the crash at all times. anyway
this is what i was able to get:

Starting program:
/home/jose/tarballs/pacman/roxterm/src/roxterm-1.18.2/src/roxterm
--appdir=/home/jose/tarballs/pacman/roxterm/src/roxterm-1.18.2

(roxterm:5053): WARNING : Failed to connect to session manager: SESSION_MANAGER environment variable not defined

Program received signal SIGSEGV, Segmentation fault.

0xb7b07777 in _gdk_window_process_expose () from /usr/lib/libgdk-x11-2.0.so.0

(gdb) bt

0 0xb7b07777 in _gdk_window_process_expose () from

/usr/lib/libgdk-x11-2.0.so.0

1 0xb7b02e07 in gdk_event_translate () from /usr/lib/libgdk-x11-2.0.so.0

2 0xb7b044a2 in _gdk_events_queue () from /usr/lib/libgdk-x11-2.0.so.0

3 0xb7b0454f in gdk_event_dispatch () from /usr/lib/libgdk-x11-2.0.so.0

4 0xb7917f72 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0

5 0xb7918750 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0

6 0xb7918dfb in g_main_loop_run () from /usr/lib/libglib-2.0.so.0

7 0xb7c73439 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0

8 0x0804fc0e in main (argc=1, argv=0xbffff804) at main.c:297

is it helpful or i need to recompile gtk libraries (i'm using arch linux)?

cheers,

jose

If you could install the debugging symbols for libgdk-x11 so you can tell the
line number it crashes on etc, and let me know the version number too, that
should help. But I think this looks like a bug in the version of GDK you've
got so you might have to report it elsewhere and/or see if there's a fixed
version you can install.

hmm.. there's no libgdk-x11 package for arch linux, could you please tell me
which package on http://www.archlinux.org/packages/?sort=&arch=&repo=&q=gdk&m
aintainer=&last_update=&flagged=&limit=50 contains
the library i need to recompile with debugging symbols?

It should be in gtk2.

thank you, here's a gdk output with debug=yes:
http://pastebin.com/1KBiU5XA

bump

I did reply, but the message has disappeared.

There are still no debugging symbols available for that backtrace but the
crash is in a different place. For this one I'd need debugging for glib2 as
well as gtk2. You have to make sure that CFLAGS includes -g when compiling and
that the debugging symbols don't get stripped when installing (done by install
-s I think) or that the debugging symbols get saved elsewhere. If I install a
-dbg package in Debian it includes files in /usr/lib/debug which mirror the
libraries in their standard locations eg
/usr/lib/debug/usr/lib/libgdk-x11-2.0.so.0.2000.1,
/usr/lib/debug/lib/libglib-2.0.so.0.2400.1.

The crash "moving" might mean it's memory/stack corruption causing random
effects, so it would probably be better to use --valgrind than --debug. Please
get the latest svn because I've altered AppRun to automatically enable ulimit
-c unlimited when --valgrind is used.

hopefully i did everything correctly (things are a little different on arch
linux than on debian-based distro). i had to try a little bit more than usual
but finally i crashed roxterm svn with valgrind on. the output's here:
http://pastebin.com/KVuisPdL

Please could you check out the latest svn (763) and see if it works correctly.
I think the trigger for the crashes would have been maximising and/or
unmaximising a window after one of its tabs had been closed.

the log comes from rev 763, actually. and no maximizing/unmaximizing is
happening here. i'm switching desktops (openbox) instead

I didn't create r763 until after I'd read message 10. Please could you svn
update (should get 764), try to reproduce the crash and upload another log if
it does crash.

with r764 i can no longer reproduce it. can you please tell when are you
planning to release a new stable?

That's all I was waiting for really, I might as well release it today.

In case you don't receiver release notifications, I released version 1.18.3
today.