CURRENT_TEST: main.1st
110225 15:52:01 [Note] PrimeBase XT (PBXT) Engine 1.0.11-7 Pre-GA loaded...
110225 15:52:01 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
110225 15:52:01  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
110225 15:52:01  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
110225 15:52:01  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
110225 15:52:02 Percona XtraDB (http://www.percona.com) 1.0.13-11.6 started; log sequence number 0
110225 15:52:02 [Warning] /home/philips/bzr/maria-5.3-mwl128/sql/mysqld: unknown option '--loose-skip-ndbcluster'
110225 15:52:02 [Warning] /home/philips/bzr/maria-5.3-mwl128/sql/mysqld: unknown variable 'loose-falcon-debug-mask=2'
110225 15:52:02 [Note] Event Scheduler: Loaded 0 events
110225 15:52:07 [Note] /home/philips/bzr/maria-5.3-mwl128/sql/mysqld: ready for connections.
Version: '5.3.0-MariaDB-alpha-debug-log'  socket: '/tmp/wl128-vardir101/current/tmp/master.sock'  port: 19300  Source distribution
110225 15:56:09 [ERROR] mysqld got signal 11 ;
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.

key_buffer_size=0
read_buffer_size=131072
max_used_connections=5
max_threads=153
threads_connected=3
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 59963 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0xad8fc28
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0xa7493360 thread_stack 0x48000
/home/philips/bzr/maria-5.3-mwl128/sql/mysqld(my_print_stacktrace+0x33) [0x87699bc]
/home/philips/bzr/maria-5.3-mwl128/sql/mysqld(handle_segfault+0x300) [0x8285667]
[0x633400]
/home/philips/bzr/maria-5.3-mwl128/sql/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*)+0x33d) [0x830aabc]
/home/philips/bzr/maria-5.3-mwl128/sql/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned long)+0x1cd) [0x83033e9]
/home/philips/bzr/maria-5.3-mwl128/sql/mysqld() [0x82a0f54]
/home/philips/bzr/maria-5.3-mwl128/sql/mysqld(mysql_execute_command(THD*)+0x719) [0x8297f63]
/home/philips/bzr/maria-5.3-mwl128/sql/mysqld(mysql_parse(THD*, char*, unsigned int, char const**)+0x26f) [0x82a34ec]
/home/philips/bzr/maria-5.3-mwl128/sql/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x8bc) [0x8295bfb]
/home/philips/bzr/maria-5.3-mwl128/sql/mysqld(do_command(THD*)+0x271) [0x82950a8]
/home/philips/bzr/maria-5.3-mwl128/sql/mysqld(handle_one_connection+0x152) [0x8292186]
/lib/libpthread.so.0() [0x821919]
/lib/libc.so.6(clone+0x5e) [0x76acce]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xb6c22dc8 is an invalid pointer
thd->thread_id=10
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file
