Re: Replication crashes when max_bin_log_size is reached
Thanks!...There is was :)
I executed resolve_stack_dump -s mysqld.sym -n mysqld.stack
and now I got:
0x8072d44 handle_segfault + 420
0x826ca28 pthread_sighandler + 184
0x829571a chunk_alloc + 1882
0x8294e71 malloc + 209
0x825149e my_malloc + 30
0x82518aa init_alloc_root + 90
0x805fbcb init_sql_alloc__FP11st_mem_rootUiUi + 27
0x807c2fb handle_one_connection + 571
0x826a1dc pthread_start_thread + 220
0x82a008a thread_start + 4
I don't know if this is valid cause I have since the crash restarted mysql. Do I have to wait until it crashes again or will this do?
Hope this helps.
Regards
Iwarson
Subject
Views
Written By
Posted
5924
February 19, 2005 08:33PM
3259
March 15, 2005 10:04AM
3649
April 20, 2005 06:29AM
3034
April 24, 2005 09:29PM
3081
April 30, 2005 02:52AM
3000
April 30, 2005 09:45AM
2914
May 01, 2005 02:29AM
2791
May 01, 2005 02:32AM
2984
May 06, 2005 01:59AM
2689
May 06, 2005 02:00AM
7780
May 11, 2005 08:12PM
3366
May 12, 2005 01:16PM
3118
May 16, 2005 04:32PM
2880
May 17, 2005 02:20AM
3068
May 17, 2005 06:53AM
2868
May 17, 2005 09:54AM
Re: Replication crashes when max_bin_log_size is reached
2956
May 17, 2005 06:23PM
3007
May 18, 2005 04:13AM
2949
May 18, 2005 08:02AM
5390
May 20, 2005 02:56PM
3800
May 23, 2005 03:30AM
2853
May 23, 2005 03:38AM
2978
May 31, 2005 08:52AM
3023
May 31, 2005 11:44AM
3089
May 02, 2005 07:31PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.