Ah, that makes sense. So it potentially could be the simple matter of telling the compiler that the type is unsigned.
--shak Chuck Simmons wrote: > Bert -- > > Your problem is not the same as Shakeel's. For you, the database is > saying that it couldn't allocate memory. For Shakeel, it is saying > that an assert failed. At about line 213, there is a right shift (X > >> Y) that is occuring. The behavior of a right shift is different > depending on whether the value being shifted is signed or unsigned. > The value is supposed to be unsigned, but the programmers forgot to > tell the compiler. This effectively means that mysql cannot allocate > more than 2GB of ram. > > " > block = buf_pool_get_nth_block(buf_pool, (ptr - frame_zero) > >> UNIV_PAGE_SIZE_SHIFT); > ut_a(block >= buf_pool->blocks); > " > > Chuck > > > Bert VdB wrote: > >> Hi, >> >> I'm sort of glad we're not the only one having this problem. >> Yesterday we had kind of the same error message on an Solaris 8 >> machine with >> 512Mb of ram. >> Our buffer_pool_size was set to 250Mb, because the other 250Mb is >> used by >> the orion-web-server. >> >> Today I will perform crash-tests on another machine and try to find >> out the >> problem. >> >> Fyi, our error log: >> ================================= >> /opt/nusphere/mysql-max-3.23.49-sun-solaris2.8-sparc/bin/mysqld: >> ready for >> connections >> mysqld got signal 10; >> This could be because you hit a bug. It is also possible that this >> binary >> or one of the libraries it was linked agaist 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=8388600 >> record_buffer=131072 >> sort_buffer=2097144 >> max_used_connections=16 >> max_connections=100 >> threads_connected=3 >> It is possible that mysqld could use up to key_buffer_size + >> (record_buffer + sort_buffer)*max_connections = 225791 K >> bytes of memory >> Hope that's ok, if not, decrease some variables in the equation >> >> 020625 15:39:58 mysqld restarted >> 020625 15:40:34 InnoDB: Database was not shut down normally. >> InnoDB: Starting recovery from log files... >> InnoDB: Starting log scan based on checkpoint at >> InnoDB: log sequence number 0 272046313 >> InnoDB: Fatal error: cannot allocate 2310548 bytes of >> InnoDB: memory with malloc! Total allocated memory >> InnoDB: by InnoDB 334012166 bytes. Operating system errno: 11 >> InnoDB: Cannot continue operation! >> InnoDB: Check if you should increase the swap file or >> InnoDB: ulimits of your operating system. >> InnoDB: On FreeBSD check you have compiled the OS with >> InnoDB: a big enough maximum process size. >> 020625 15:40:37 mysqld ended >> ==================================================================== >> >> >> -----Original Message----- >> From: Shakeel Sorathia [mailto:[EMAIL PROTECTED]] >> Sent: Tuesday, June 25, 2002 21:01 >> To: [EMAIL PROTECTED] >> Subject: innodb bug >> >> >> I've been having a problem with innodb lately. We just upgraded one >> of our machine to have 4 GB of ram in it. However, whenever I make >> the innodb_buffer_pool_size greater then 2048M It crashes with the >> following in the error log. It's 3.23.51 running on a Solaris 8 >> Ultrasparc II machine with 4 GB ram. Is the limit 2gb of ram, or is >> there something that I'm doing wrong? Thanks for the help! >> >> --shak >> >> 020625 12:57:14 mysqld started >> InnoDB: Assertion failure in thread 1 in file ../include/buf0buf.ic >> line 214 >> InnoDB: We intentionally generate a memory trap. >> InnoDB: Send a detailed bug report to [EMAIL PROTECTED] >> 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 agaist 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=8388600 >> record_buffer=131072 >> sort_buffer=1048568 >> max_used_connections=0 >> max_connections=1024 >> threads_connected=0 >> It is possible that mysqld could use up to >> key_buffer_size + (record_buffer + sort_buffer)*max_connections = >> 1187831 K >> bytes of memory >> Hope that's ok, if not, decrease some variables in the equation >> >> 020625 12:57:54 mysqld ended >> >> >> > > --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
