| Bug #18964 | return 0 instead of DBUG_RETURN(0) in sql_base.cc::open_table() | ||
|---|---|---|---|
| Submitted: | 10 Apr 2006 15:59 | Modified: | 27 Apr 2006 2:56 |
| Reporter: | Andrey Hristov | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 5.0.20 | OS: | Any (All) |
| Assigned to: | Tatiana Azundris Nuernberg | CPU Architecture: | Any |
[10 Apr 2006 16:22]
MySQL Verification Team
Thank you for the bug report.
[19 Apr 2006 23:02]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/5181
[20 Apr 2006 15:38]
Tatiana Azundris Nuernberg
fixed in 5.0.21
[27 Apr 2006 2:56]
Paul DuBois
Noted in 5.0.21 changelog. A missing <literal>DBUG_RETURN()</literal> caused the server to emit a spurious error message: <literal>missing DBUG_RETURN or DBUG_VOID_RETURN macro in function "open_table"</literal>. (Bug #18964)

Description: the macro DBUG_RETURN() is not used in the following code which exists in 5.0 onwards if (check_stack_overrun(thd, STACK_MIN_SIZE_FOR_OPEN, (char *)&alias)) return 0; Because of this the server emits an error message: mysqld: missing DBUG_RETURN or DBUG_VOID_RETURN macro in function "open_table" How to repeat: See the source