[MDEV-4286] Server crashes in Protocol_text::store, stack smashing detected Created: 2013-03-17  Updated: 2013-03-18  Resolved: 2013-03-18

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 5.3.12
Fix Version/s: 5.3.13

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates

 Description   

The root cause of the problem might exist in 5.5 and 10.0 too, but I am not getting a crash there, no valgrind errors either, and query results seem to be reasonable (shown at the end of the description).

CREATE TABLE t1 (i INT, d DATE) ENGINE=MyISAM;
INSERT INTO t1 VALUES (1, '2008-10-02'), (2, '2010-12-12');
SELECT d, AVG( EXPORT_SET( 13, 'Y', ( SHA( i ) ) ) ), GROUP_CONCAT( d ) 
FROM t1 GROUP BY d ORDER BY i;

Stack trace on 5.3 (although not very helpful):

#5  <signal handler called>
#6  0x00007f191a4fd066 in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#7  0x00007f191a4fdd7d in _Unwind_Backtrace () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#8  0x00007f191a80e9c8 in __GI___backtrace (array=<optimized out>, size=64) at ../sysdeps/x86_64/../ia64/backtrace.c:110
#9  0x00007f191a7783af in __libc_message (do_abort=2, fmt=0x7f191a87fe3f "*** %s ***: %s terminated\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:180
#10 0x00007f191a80e807 in __GI___fortify_fail (msg=0x7f191a87fe27 "stack smashing detected") at fortify_fail.c:32
#11 0x00007f191a80e7d0 in __stack_chk_fail () at stack_chk_fail.c:29
#12 0x000000000066c629 in Protocol_text::store (this=0x38979b8, field=0x7f18b4018928) at protocol.cc:1095
#13 0x2020202020202020 in ?? ()
#14 0x2020202020202020 in ?? ()
#15 0x2020202020202020 in ?? ()
#16 0x2020202020202020 in ?? ()
#17 0x2020202020202020 in ?? ()
#18 0x2020202020202020 in ?? ()
...
#243 0x000000000389a188 in ?? ()
#244 0x0000000000000000 in ?? ()

revision-id: igor@askmonty.org-20130308082526-5w0b7gya5ed97uzo
revno: 3635
branch-nick: 5.3

Reproducible on older revisions, too.

Built with BUILD/compile-pentium-valgrind-max-no-ndb; was also reproducible with BUILD/compile-pentium-debug-max-no-ndb.
I tried 3 different machines, 2 Ubuntus and Gentoo, got the crash on each of them.

Results on 5.5 (I don't see a problem here):

INSERT INTO t1 VALUES (1, '2008-10-02'), (2, '2010-12-12');
SELECT d, AVG( EXPORT_SET( 13, 'Y', ( SHA( i ) ) ) ), GROUP_CONCAT( d ) 
FROM t1 GROUP BY d ORDER BY i;
d	AVG( EXPORT_SET( 13, 'Y', ( SHA( i ) ) ) )	GROUP_CONCAT( d )
2008-10-02	0	2008-10-02
2010-12-12	0	2010-12-12



 Comments   
Comment by Sergei Golubchik [ 2013-03-18 ]

pushed in 5.3

Generated at Thu Feb 08 06:55:14 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.