Paul Wise wrote:
> Hi,
>
> You don't seem to be taking care of mysql-gui-tools very well, will you
> update it before lenny, or should I NMU the patch that fixes #466623,
> #485864 and #489047? Perhaps you would like to orphan it?
>
The only constructive comment upstream is,
[27 Sep 2007 15:33] Richard Fuller
I've been playing with this a bit more. It hangs in
MQQueryDispatcher::get_sps in the
while(!req->is_complete()) loop, as reported by another poster.
complete is getting setting to true, then mysteriously being zeroed.
Padding the
definition in MQQueryDispatcher.h, like so:
int padding[10240];
volatile bool complete;
int padding2[10240];
makes it work reliably, so I guess something is getting written to the
wrong place. With
less padding it works for opening one schema at a time, but open several
and it hangs.
It's mildly suspicious that the loop is commented out of
MQQueryDispatcher::get_tables.
Which would mean applying the "patch" doesn't solve the problem. It
would just delay it, or cause other crashes in the application or even
screw up your data.
And the problem is, I can't reproduce the problem. I've cleared my
~/.mysqlgui and everything works perfectly. If you guys are still
getting this problem after clearing the settings, I'll add the hack if
it fixes it for you. But I think the real problem is some uninitialized
pointer or something.
Recompile with debug symbols, and run under valgrind. Does it
run/crashes? Can someone send me the output of valgrind?
When I connect to a schema, the only related item I get is,
==2130== Invalid read of size 1
==2130== at 0x81436E0: MQQueryDispatcher::get_sps(Glib::ustring
const&, Glib::ustring const&) (MQQueryDispatcher.h:70)
==2130== by 0x81C4F31: MQBaseModule::schemata_fetch_sps(Glib::ustring
const&, Glib::ustring const&, MYX_SCHEMA_STORED_PROCEDURES*&)
(MQBaseModule.cc:41)
And, the first like is the is_complete call. This kind of points towards
the idea that the class wasn't allocated?? Maybe some race condition.
My complete valgrind output is at,
http://bugs.mysql.com/file.php?id=9623&text=1
- Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
