Crash in MySQL-4.1 (since the ON DUPLICATE KEY UPDATE code)

Hi,

I pulled yesterday the latest 4.1 source, with ON DUPLICATE KEY UPDATE code.
Since then, I'm experiencing some random crashes with the following stack
trace :

0x80a2d91 handle_segfault + 481
0x828e1d8 pthread_sighandler + 176
0x828c833 pthread_mutex_lock + 11
0x80dfacb write_delayed(THD*, st_table*, enum_duplicates, char*, unsigned,
bool) + 59
0x80dd4b7 mysql_insert(THD*, st_table_list*, List&, List
>&, List&, List&, enum_duplicates) + 2471
0x80b13ee mysql_execute_command(THD*) + 8622
0x80b42d8 mysql_parse(THD*, char*, unsigned) + 248
0x80ae394 dispatch_command(enum_server_command, THD*, char*, unsigned) + 852
0x80ae026 do_command(THD*) + 118
0x80ad90e handle_one_connection + 910
0x828bbfa pthread_start_thread + 218
0x82bff1a thread_start + 4

How-to-repeat :

I don't know yet which query crash the server, I will investigate.

Regards,
Jocelyn


------------------------------------------------------------ ---------
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 bugs-thread13191@lists.mysql.com
To unsubscribe, e-mail

Re: Crash in MySQL-4.1 (since the ON DUPLICATE KEY UPDATE code)

Hi,

Yes I know, but perhaps the stack trace can give you some clues, since I
never encountered crashes before ON DUPLICATE KEY enhancement, and the crash
occurs in sql_insert.cc ;)
(I'm waiting for my server to crash again).

Regards,
Jocelyn
----- Original Message -----
From: "Sinisa Milivojevic"
To:
Cc: ;
Sent: Tuesday, December 03, 2002 12:03 PM
Subject: Re: Crash in MySQL-4.1 (since the ON DUPLICATE KEY UPDATE code)


> jocelyn fournier writes:
> > Hi,
> >
> > I pulled yesterday the latest 4.1 source, with ON DUPLICATE KEY UPDATE
code.
> > Since then, I'm experiencing some random crashes with the following
stack
> > trace :
> >
> >
> > How-to-repeat :
> >
> > I don't know yet which query crash the server, I will investigate.
> >
> > Regards,
> > Jocelyn
> >
>
> As you well know, we truly require a repeatable test case.
>
> --
> Regards,
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
> /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
> <___/ www.mysql.com
>
>
>
>


------------------------------------------------------------ ---------
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 bugs-thread13196@lists.mysql.com
To unsubscribe, e-mail

Re: Crash in MySQL-4.1 (since the ON DUPLICATE KEY UPDATE code)

jocelyn fournier writes:
> Hi,
>
> I pulled yesterday the latest 4.1 source, with ON DUPLICATE KEY UPDATE code.
> Since then, I'm experiencing some random crashes with the following stack
> trace :
>
>
> How-to-repeat :
>
> I don't know yet which query crash the server, I will investigate.
>
> Regards,
> Jocelyn
>

As you well know, we truly require a repeatable test case.

--
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www.mysql.com


------------------------------------------------------------ ---------
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 bugs-thread13195@lists.mysql.com
To unsubscribe, e-mail

Re: Crash in MySQL-4.1 (since the ON DUPLICATE KEY UPDATE code)

Hi!

On Dec 03, jocelyn fournier wrote:
> Hi,
>
> I pulled yesterday the latest 4.1 source, with ON DUPLICATE KEY UPDATE code.
> Since then, I'm experiencing some random crashes with the following stack
> trace :
>
> 0x80a2d91 handle_segfault + 481
> 0x828e1d8 pthread_sighandler + 176
> 0x828c833 pthread_mutex_lock + 11
> 0x80dfacb write_delayed(THD*, st_table*, enum_duplicates, char*, unsigned, bool) + 59
> 0x80dd4b7 mysql_insert(THD*, st_table_list*, List&, List>&, List&, List&, enum_duplicates) + 2471
> 0x80b13ee mysql_execute_command(THD*) + 8622
> 0x80b42d8 mysql_parse(THD*, char*, unsigned) + 248
> 0x80ae394 dispatch_command(enum_server_command, THD*, char*, unsigned) + 852
> 0x80ae026 do_command(THD*) + 118
> 0x80ad90e handle_one_connection + 910
> 0x828bbfa pthread_start_thread + 218
> 0x82bff1a thread_start + 4

No, no clue here :(
ON ... UPDATE should not interfere with the old code,
and write_delayed() cannot be called when ON ... UPDATE is used.

Well, the latter is for sure.
The former - it should not but it could :(
Still, I didn't find anything looking at the code.

So, I'm wating for you test case :)

> How-to-repeat :
>
> I don't know yet which query crash the server, I will investigate.
>
> Regards,
> Jocelyn
>
Regards,
Sergei

--
MySQL Development Team
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/
/_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
<___/

------------------------------------------------------------ ---------
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 bugs-thread13197@lists.mysql.com
To unsubscribe, e-mail