data_dictionary plugin show_tables assert hit

Bug #550090 reported by Andrew Hutchings on 2010-03-28
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

On a fresh installation of drizzle:

drizzle> use data_dictionary
Reading table information for completion of table and column names
    You can turn off this feature to get a quicker startup with -A

Database changed
drizzle> select * from show_tables;
drizzle_state_read:lost connection to server (EOF)
No connection. Trying to reconnect...
drizzle_state_connect:could not connect
Can't connect to the server

drizzled: plugin/schema_dictionary/ ShowTables::Generator::Generator(drizzled::Field**): Assertion `not schema_name.empty()' failed.
100328 8:56:53 - drizzled got signal 6;
This could be because you hit a bug. It is also possible that this binary
 or one of the libraries it was linked against is corrupt, improperly built,
 or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

It is possible that drizzled could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*thread_count
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

session: 0x26dcda0
Attempting backtrace. You can use the following information to find out
where drizzled died. If you see no messages after this, something went
terribly wrong...
sbin/drizzled() [0x63def3]
sbin/drizzled(drizzled::print_stacktrace(unsigned char*, unsigned long)+0xe) [0x63e04e]
sbin/drizzled(handle_segfault+0x2ed) [0x50c70d]
/lib/ [0x7f2ef41d38f0]
/lib/ [0x7f2ef3e75a75]
/lib/ [0x7f2ef3e795c0]
/lib/ [0x7f2ef3e6e941]
/home/linuxjedi/Programming/Builds/drizzle-bug-308381/lib/drizzle/**)+0x141) [0x7f2ee1890561]
/home/linuxjedi/Programming/Builds/drizzle-bug-308381/lib/drizzle/**)+0x29) [0x7f2ee18914b9]
/home/linuxjedi/Programming/Builds/drizzle-bug-308381/lib/drizzle/ [0x7f2ee006d46f]
sbin/drizzled(drizzled::Cursor::ha_rnd_init(bool)+0x28) [0x502198]
sbin/drizzled(drizzled::init_read_record(drizzled::st_read_record*, drizzled::Session*, drizzled::Table*, drizzled::optimizer::SqlSelect*, int, bool)+0x332) [0x5e0502]
sbin/drizzled(drizzled::join_init_read_record(drizzled::JoinTable*)+0x68) [0x6156e8]
sbin/drizzled(drizzled::sub_select(drizzled::JOIN*, drizzled::JoinTable*, bool)+0x61) [0x6158d1]
sbin/drizzled(drizzled::do_select(drizzled::JOIN*, drizzled::List<drizzled::Item>*, drizzled::Table*)+0x154) [0x619ae4]
sbin/drizzled(drizzled::JOIN::exec()+0x55f) [0x595caf]
sbin/drizzled(drizzled::mysql_select(drizzled::Session*, drizzled::Item***, drizzled::TableList*, unsigned int, drizzled::List<drizzled::Item>&, drizzled::Item*, unsigned int, drizzled::order_st*, drizzled::order_st*, drizzled::Item*, unsigned long, drizzled::select_result*, drizzled::Select_Lex_Unit*, drizzled::Select_Lex*)+0x102) [0x616f22]
sbin/drizzled(drizzled::handle_select(drizzled::Session*, drizzled::LEX*, drizzled::select_result*, unsigned long)+0x160) [0x6177f0]
sbin/drizzled(drizzled::execute_sqlcom_select(drizzled::Session*, drizzled::TableList*)+0xd5) [0x6111c5]
sbin/drizzled(drizzled::mysql_parse(drizzled::Session*, char const*, unsigned int)+0x1b6) [0x610ed6]
sbin/drizzled(drizzled::dispatch_command(drizzled::enum_server_command, drizzled::Session*, char*, unsigned int)+0x3fd) [0x6118dd]
sbin/drizzled(drizzled::Session::executeStatement()+0x8f) [0x5e3c8f]
sbin/drizzled(drizzled::Session::run()+0x112) [0x5e59d2]
/home/linuxjedi/Programming/Builds/drizzle-bug-308381/lib/drizzle/ [0x7f2ee1057062]
/lib/ [0x7f2ef41ca9ca]
/lib/ [0x7f2ef3f286dd]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
session->query at 0x1f18b58 = select * from show_tables

Related branches

Lee Bieber (kalebral) on 2010-04-21
Changed in drizzle:
assignee: nobody → ziminq (ziminq)
status: New → Confirmed
Lee Bieber (kalebral) wrote :

Andrew, I can't reproduce this anymore, would you also try again.

Andrew Hutchings (linuxjedi) wrote :

Cannot reproduce in latest trunk, marking invalid

Changed in drizzle:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers