Bug 82189 - bad source code
bad source code
Status: CLOSED UPSTREAM
Product: Red Hat Linux
Classification: Retired
Component: mysql (Show other bugs)
8.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Patrick Macdonald
:
: 105840 110767 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-19 05:30 EST by d.binderman
Modified: 2007-04-18 12:50 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-06-10 15:12:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description d.binderman 2003-01-19 05:30:44 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.6 [en-gb]C-CCK-MCD NetscapeOnline.co.uk  (Win98; I)

Description of problem:

Hello there,

I just tried to compile package mysql-3.23.52-3 from Redhat 8.0

The compiler said

ut0ut.c:59: warning: right shift count >= width of type
dict0load.c:340: warning: too many arguments for format
log0recv.c:1384: warning: too few arguments for format
log0recv.c:1401: warning: too few arguments for format
log0recv.c:1429: warning: too few arguments for format

Here is an untested patch to shut up the compiler.

*** ./innobase/log/log0recv.c.old	2003-01-16 21:46:23.000000000 +0000
--- ./innobase/log/log0recv.c	2003-01-16 21:48:18.000000000 +0000
***************
*** 1381,1387 ****
  							&success);
  			if (!success) {
  				printf(
! "InnoDB: Error: cannot open %lu'th data file %s\n", nth_file);
  
  				exit(1);
  			}
--- 1381,1387 ----
  							&success);
  			if (!success) {
  				printf(
! "InnoDB: Error: cannot open %lu'th data file %s\n", nth_file, data_files[nth_file]);
  
  				exit(1);
  			}
***************
*** 1398,1404 ****
  			if (!success) {
  				printf(
  "InnoDB: Error: cannot read page no %lu from %lu'th data file %s\n",
! 				nth_page_in_file, nth_file);
  
  				exit(1);
  			}
--- 1398,1404 ----
  			if (!success) {
  				printf(
  "InnoDB: Error: cannot read page no %lu from %lu'th data file %s\n",
! 				nth_page_in_file, nth_file, data_files[nth_file]);
  
  				exit(1);
  			}
***************
*** 1426,1432 ****
  			if (!success) {
  				printf(
  "InnoDB: Error: cannot write page no %lu to %lu'th data file %s\n",
! 				nth_page_in_file, nth_file);
  
  				exit(1);
  			}
--- 1426,1432 ----
  			if (!success) {
  				printf(
  "InnoDB: Error: cannot write page no %lu to %lu'th data file %s\n",
! 				nth_page_in_file, nth_file, data_files[nth_file]);
  
  				exit(1);
  			}

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. compile the program
2.
3.
    

Additional info
Comment 1 Patrick Macdonald 2003-02-19 10:19:47 EST
Yes, these problems still exist in the current production (3.23.55) release.
We'll notify upstream.
Comment 2 Patrick Macdonald 2003-06-10 15:12:39 EDT
This has been fixed, according to the bug report, in MySQL 4.0.

Please see MySQL bug 287.

http://bugs.mysql.com/bug.php?id=287
Comment 3 Patrick Macdonald 2003-09-29 09:54:45 EDT
*** Bug 105840 has been marked as a duplicate of this bug. ***
Comment 4 Patrick Macdonald 2003-11-24 10:26:38 EST
*** Bug 110767 has been marked as a duplicate of this bug. ***
Comment 5 David Binderman 2004-11-23 06:07:00 EST
>This has been fixed, according to the bug report, in MySQL 4.0.

But when does MySQL 4.0 get into Fedora ?

In Fedora Core 3, the three problems in file log0recv.c still exist.

This bug report is nearly two years old and still isn't completely fixed.
Comment 6 Patrick Macdonald 2004-11-23 10:22:39 EST
It has been fixed but Fedora Core still ships MySQL 3.23 due to
legal issues.  

Note You need to log in before you can comment on or make changes to this bug.