|
ru.linux
- RU.LINUX ---------------------------------------------------------------------
From : Alexander N. Skovpen 2:5020/9696 01 Sep 2004 23:32:12
To : Valentin Nechayev
Subject : P4 optimization
--------------------------------------------------------------------------------
01 Sep 04 10:26, you wrote to me:
ANS>> дабавил флаги оптимизации в переменную окружения, скомпилил mysql
ANS>> и словил жопу
ANS>> :-( (безфлагов оптимизации такого не было)...что именно я сделал
ANS>> не так? :-)
VN> Ёр-Оол Гуй тебя знает, что ты там сделал не так.
VN> Hо оставив -fomit-frame-pointer ты не сможешь даже понять, что
VN> произошло.
:-)
=== начнём mysql.log ===
040831 20:04:53 mysqld started
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=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 217599
K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=(nil)
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...
Cannot determine thread, fp=0xbffff578, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x813520c
0x400504be
0x8161a89
0x81376ed
0x813580c
0x401efaf7
0x80cfa95
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/en/Using_stack_trace.html and follow
instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
040831 20:04:53 mysqld ended
=== закончим mysql.log ===
Alexander
... Tempora mutantur et nos mutamur in illis(c)
--- ННННННННЛЛНЛЛНЛНННН
* Origin: НКННОКНКНООН (2:5020/9696)
Вернуться к списку тем, сортированных по: возрастание даты уменьшение даты тема автор
|
P4 optimization 