From: James A. T. <tr...@de...> - 2002-01-09 22:51:13
|
Hello, Do you have any pointers to debugging a crash in gramps? This would be so easy in C. It only crashes when exiting from the event dialog - using either OK or Cancel. A dialog pops up stating 'Application "/usr/bin/python" (process 17636) has crashed due to a fatal error. (Segmentation fault)'. Running the program with 'python -d' doesn't help. This is on a Debian woody system with 0.7.0 installed. It was working fine until about a week ago. I believe the problems started when I upgraded one of python, python-glade or python-gnome but that is just a guess. I think the upgrade may have switched the last of the components from using python 1.5 to python 2.1. I tried recompiling gramps (originally compiled using python 1.5) on a fully python 2.1 system and it made no difference. On a different topic, is there any work being done on a tutorial for creating a good database? What I mean by this is explaining recommended ways of storing dates (especially uncertain ones, like 'spring 1940-1941' or 'May 21' with no year and teaching standard gedcom keywords like BEFORE and ABOUT) and storing places, e.g. in an event, do you put everything in the place, like 'St. Mary's, Baltimore, MD'? I actually know the answer to some of the above, but not all of them. A document that helps people make a robust database would be a great asset. -- James (Jay) Treacy tr...@de... |
From: Don A. <dal...@us...> - 2002-01-10 02:19:34
|
On Wed, 2002-01-09 at 15:51, James A. Treacy wrote: > Hello, > > Do you have any pointers to debugging a crash in gramps? This would be > so easy in C. > > It only crashes when exiting from the event dialog - using either OK > or Cancel. A dialog pops up stating 'Application "/usr/bin/python" > (process 17636) has crashed due to a fatal error. (Segmentation > fault)'. Running the program with 'python -d' doesn't help. Normally, debugging in python is much easier than in C, as long as the bug is in the python code instead of the any C libraries. Typically when a problem like this occurs, it is because we are tripping a bug in the Gtk libraries. GDB can be used here. Start GDB in the gramps installation directory (typically /usr/local/share/gramps or /usr/share/gramps) and run python. When you get the gdb prompt back, run it with "gramps.py" as the argument. It will take a while to start up, but then you can run the program. When python crashes, you can get a trace back. $ gdb /usr/bin/python GNU gdb Red Hat Linux (5.1-1) Copyright 2001 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 "i386-redhat-linux"... (no debugging symbols found)... (gdb) run gramps.py Starting program: /usr/bin/python gramps.py [New Thread 1024 (LWP 2789)] > This is on a Debian woody system with 0.7.0 installed. It was working > fine until about a week ago. I believe the problems started when I > upgraded one of python, python-glade or python-gnome but that is > just a guess. I think the upgrade may have switched the last of the > components from using python 1.5 to python 2.1. You will need a python-glade and python-gnome which are compatible with python 2.1. The object code libraries are not fully compatible. > I tried recompiling gramps (originally compiled using python 1.5) on > a fully python 2.1 system and it made no difference. > On a different topic, is there any work being done on a tutorial > for creating a good database? What I mean by this is explaining > recommended ways of storing dates (especially uncertain ones, like > 'spring 1940-1941' or 'May 21' with no year and teaching standard > gedcom keywords like BEFORE and ABOUT) and storing places, e.g. in > an event, do you put everything in the place, like 'St. Mary's, > Baltimore, MD'? > I actually know the answer to some of the above, but not all of them. > A document that helps people make a robust database would be a great > asset. Shawn Ann Griffith is heading up the documentation effort, so eventually we will have a good manual to help describe this type of stuff. She is looking for help, if anyone wants to help. Just mention it on this list, and I'm sure she'll contact you rather quickly. I'll try to provide a few answers to the above: gramps tries its best to handle all kinds of date formats. It will accept anything, but if it can't recoginize it, it will just keep it as a text string. Partial dates can be entered in, and gramps does its best. It should recongize May 21 as a valid date, but will not recognize "spring 1940-1941". It should also accept things like: about 1920 around 1920 before 1920 after 1920 bef 1920 bef. 1920 aft 1920 est. 1920 circa. 1920 from 1920 to January 3, 1921 between 2/3/1920 and JAN 4, 1921 Places are fairly flexible. The string that you see in the event window for a place is a title of a place. It can be anything that you want. The Place View allows you to specify more information about the place, and in a more structured format (city, state, country, longitute, latitude, alternate names, etc.) The title, which appears in the menu, is whatever you want it to be. Don -- Don Allingham dal...@us... http://gramps.sourceforge.net |
From: James A. T. <tr...@de...> - 2002-01-10 03:37:54
|
On Wed, Jan 09, 2002 at 07:19:27PM -0700, Don Allingham wrote: > > GDB can be used here. Start GDB in the gramps installation directory > (typically /usr/local/share/gramps or /usr/share/gramps) and run python. > When you get the gdb prompt back, run it with "gramps.py" as the > argument. It will take a while to start up, but then you can run the > program. When python crashes, you can get a trace back. > Great. Worked like a charm. Here is the result of a backtrace after it segfaults: (gdb) backtrace #0 0x402c6eae in gtk_color_selection_dialog_new () from /usr/lib/libgtk-1.2.so.0 #1 0x4063029d in gnome_entry_new () from /usr/lib/libgnomeui.so.32 #2 0x08510648 in ?? () Cannot access memory at address 0x1 This occurred right after clicking Cancel in the event window. -- James (Jay) Treacy tr...@de... |
From: Don A. <dal...@us...> - 2002-01-10 05:39:03
|
On Wed, 2002-01-09 at 20:37, James A. Treacy wrote: > (gdb) backtrace > #0 0x402c6eae in gtk_color_selection_dialog_new () from /usr/lib/libgtk-1.2.so.0 > #1 0x4063029d in gnome_entry_new () from /usr/lib/libgnomeui.so.32 > #2 0x08510648 in ?? () This is really odd, because the event editor does not use either the color selection dialog or the GnomeEntry widget. Are the python-gnome and the python-glade modules compiled for python 2.1? Don -- Don Allingham dal...@us... http://gramps.sourceforge.net |
From: James A. T. <tr...@de...> - 2002-01-10 07:00:49
|
On Wed, Jan 09, 2002 at 10:38:56PM -0700, Don Allingham wrote: > On Wed, 2002-01-09 at 20:37, James A. Treacy wrote: > > (gdb) backtrace > > #0 0x402c6eae in gtk_color_selection_dialog_new () from /usr/lib/libgtk-1.2.so.0 > > #1 0x4063029d in gnome_entry_new () from /usr/lib/libgnomeui.so.32 > > #2 0x08510648 in ?? () > > This is really odd, because the event editor does not use either the > color selection dialog or the GnomeEntry widget. > > Are the python-gnome and the python-glade modules compiled for python > 2.1? > It is difficult to say since dependencies aren't tracked as well (automatically) for non-compiled code. Anyway, I just recompiled python-gtk, python-gdk-imlib, python-glade and python-gnome and it still crashes in the same place. -- James (Jay) Treacy tr...@de... |
From: Don A. <dal...@us...> - 2002-01-10 14:42:27
|
I'm at kind of a loss here. I've posted the question on the PyGTK mailing list. Hopefully I'll here something back from there. Don On Thu, 2002-01-10 at 00:00, James A. Treacy wrote: > On Wed, Jan 09, 2002 at 10:38:56PM -0700, Don Allingham wrote: > > On Wed, 2002-01-09 at 20:37, James A. Treacy wrote: > > > (gdb) backtrace > > > #0 0x402c6eae in gtk_color_selection_dialog_new () from /usr/lib/libgtk-1.2.so.0 > > > #1 0x4063029d in gnome_entry_new () from /usr/lib/libgnomeui.so.32 > > > #2 0x08510648 in ?? () > > > > This is really odd, because the event editor does not use either the > > color selection dialog or the GnomeEntry widget. > > > > Are the python-gnome and the python-glade modules compiled for python > > 2.1? > > > It is difficult to say since dependencies aren't tracked as well > (automatically) for non-compiled code. Anyway, I just recompiled > python-gtk, python-gdk-imlib, python-glade and python-gnome and > it still crashes in the same place. > > -- > James (Jay) Treacy > tr...@de... > > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel -- Don Allingham dal...@us... http://gramps.sourceforge.net |