10 messages in com.mysql.lists.bugsRe: 3.23.42 first crash (fwd)| From | Sent On | Attachments |
|---|---|---|
| Martin MOKREJŠ | 11 Sep 2001 08:11 | |
| Michael Widenius | 12 Sep 2001 04:25 | |
| Martin MOKREJŠ | 12 Sep 2001 06:09 | |
| Martin MOKREJŠ | 17 Sep 2001 05:34 | |
| Sasha Pachev | 17 Sep 2001 06:23 | |
| Martin MOKREJŠ | 17 Sep 2001 07:35 | |
| Michael Widenius | 18 Sep 2001 04:36 | |
| Martin MOKREJŠ | 18 Sep 2001 09:11 | |
| Michael Widenius | 18 Sep 2001 10:47 | |
| Martin MOKREJŠ | 19 Sep 2001 07:25 |
| Subject: | Re: 3.23.42 first crash (fwd) |
|---|---|
| From: | Michael Widenius (mon...@mysql.com) |
| Date: | 09/18/2001 10:47:35 AM |
| List: | com.mysql.lists.bugs |
Hi!
"mmokrejs" == mmokrejs <iso-8859-2> writes:
<cut>
mmokrejs> Hmm, I tried to repeat it: used all available databases and runned
"show
mmokrejs> tables", but no luck, it worked this time. I also tried to repeat the
commands
mmokrejs> found in log which crashed mysqld, no luck.
Take a look at the tests/fork_big.pl script that comes with the MySQL source distribution. It should not be that hard to tune this to be more close with your application. If you can get this to crash, there is a big chance that we could use the modified script to repeat and fix the problem
mmokrejs> Bello I'm summarizing the facts, please ignore the stupid way the sql
application is written.
mmokrejs> I already asked the coders here to fix their code. ;)
<cut>
Unfortunately the stack traces doesn't tell us what is going wrong. MySQL should not crash on simple queries like this! There must be some unknown factor that we are not aware of yet that makes your case different from the standard case.
Regards, Monty