GNOME Bugzilla – Bug 98472
Mergeant & MySqlplugin crash
Last modified: 2004-12-22 21:47:04 UTC
Package: mergeant Severity: major Version: 0.8.199 Synopsis: Mergeant & MySqlplugin crash Bugzilla-Product: mergeant Bugzilla-Component: General BugBuddy-GnomeVersion: 2.0 (2.0.5) Description: Description of Problem: Steps to reproduce the problem: 1. Connect to a mysql db (remote or local) 2. In tables & view choose a table, right-click Properties 3. or in query click new query, the same Actual Results: Crash Expected Results: How often does this happen? Always Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/mergeant' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 22735)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x40df72e9 in wait4 () from /lib/libc.so.6
+ Trace 30373
Thread 1 (Thread 16384 (LWP 22735))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-11-14 04:52 ------- The original reporter (ettore@btbs.unimib.it) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, malerba@gnome-db.org.
use HOTFIX in #98670 with: vi object-selector-ext.c +211 change 2 lines with comments to: get_dbfield_cols (DbField *field, guint nbcols) { gchar *str=NULL; //asure str is well defined g_return_val_if_fail (field && IS_DB_FIELD (field), NULL); g_return_val_if_fail (nbcols == 1, NULL); if(field->type != NULL) //don't dereference type if it's NULL if (field->length >= 0)
This patch would fix that crashing but does not solve the problem that field->type appears to be NULL which should never be the case. I think we should look at the mysql provider and particulary to: -> the ident of known data types -> the ident of the data type returned for each table's field The order in which data are collected is: -> get a list of known data types and create a ServerDataType object for each data type -> for each field in each table, get info on the field and try to find the corresponding ServerDataType object. Obviously this step has a problem. I don't have a mysql server at hand so I can't do the testing myself.
Re-assigning to mysql provider then
This should be fixed now. Please check latest versions and re-open if not.