Bug #27171 mysqlbinlog produces different output depends from option -R

Description:
mysqlbinlog data/foo.bin and mysqlbinlog -R foo.bin produce different output

How to repeat:
Run 

mysqlbinlog -u root -pxxxxxx -h dbnj07a.int --database=rhuddleston_nj3 --start-position=18351401 --stop-position=18739540 -R replicatelogs.000030 | tail

and then

mysqlbinlog --database=rhuddleston_nj3 --start-position=18351401 --stop-position=18739540 /data/binlogs/replicatelogs.000030 | tail

on attached hidden binary log file. There is no last COMMIT in the output of mysqlbinlog -R ...

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/22647

ChangeSet@1.2488, 2007-03-22 16:55:39+02:00, serg@sergbook.mysql.com +1 -0
  Bug#27171 mysqlbinlog produces different output depends from option -R
  Server starts any binlog dump from Format_description_log_event,
  this shifted all offset calculations in mysqlbinlog and made it
  to stop the dump earlier than --stop-position. Now mysqlbinlog
  takes Format_description_log_event into account

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/22654

ChangeSet@1.2488, 2007-03-22 17:51:05+02:00, serg@sergbook.mysql.com +3 -0
  Bug#27171 mysqlbinlog produces different output depends from option -R
  Server starts any binlog dump from Format_description_log_event,
  this shifted all offset calculations in mysqlbinlog and made it
  to stop the dump earlier than --stop-position. Now mysqlbinlog
  takes Format_description_log_event into account

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/22673

ChangeSet@1.2406, 2007-03-22 19:27:01+02:00, serg@sergbook.mysql.com +3 -0
  Bug#27171 mysqlbinlog produces different output depends from option -R
  Server starts any binlog dump from Format_description_log_event,
  this shifted all offset calculations in mysqlbinlog and made it
  to stop the dump earlier than --stop-position. Now mysqlbinlog
  takes Format_description_log_event into account

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/22680

ChangeSet@1.2406, 2007-03-22 20:55:59+02:00, serg@sergbook.mysql.com +3 -0
  Bug#27171 mysqlbinlog produces different output depends from option -R
  Server starts any binlog dump from Format_description_log_event,
  this shifted all offset calculations in mysqlbinlog and made it
  to stop the dump earlier than --stop-position. Now mysqlbinlog
  takes Format_description_log_event into account

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/23504

ChangeSet@1.2428, 2007-04-02 09:43:39+02:00, serg@janus.mylan +1 -0
  Bug#27171 mysqlbinlog produces different output depends from option -R
  a better fix, that works with 4.1 servers which don't send a fake
  Format_description_log_event.

comments sent by mail.

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/24170

ChangeSet@1.2428, 2007-04-10 15:26:35+02:00, serg@janus.mylan +1 -0
  Bug#27171 mysqlbinlog produces different output depends from option -R
  a better fix, that works with 4.1 servers which don't send a fake
  Format_description_log_event.

pushed in 5.0-marvel

Pushed into 5.1.18-beta

Pushed into 5.0.42

Noted in 5.0.42, 5.1.18 changelogs.

mysqlbinlog produced different output with the -R option than without
it.

The patch for this bug also fixed BUG#27037.