I'm getting the same error after upgrading to 2.4 on Mavericks 10.9.2.

2014-05-13 13:36:11 8225 [Note] Plugin 'FEDERATED' is disabled.
2014-05-13 13:36:11 8225 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-05-13 13:36:11 8225 [Note] InnoDB: The InnoDB memory heap is disabled
2014-05-13 13:36:11 8225 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-05-13 13:36:11 8225 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-05-13 13:36:11 8225 [Note] InnoDB: Not using CPU crc32 instructions
2014-05-13 13:36:11 8225 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-05-13 13:36:11 8225 [Note] InnoDB: Completed initialization of buffer pool
2014-05-13 13:36:11 8225 [Note] InnoDB: Highest supported file format is Barracuda.
2014-05-13 13:36:11 8225 [Note] InnoDB: 128 rollback segment(s) are active.
2014-05-13 13:36:11 8225 [Note] InnoDB: Waiting for purge to start
2014-05-13 13:36:11 8225 [Note] InnoDB: 5.6.17 started; log sequence number 1600627
2014-05-13 13:36:12 8225 [Note] Server hostname (bind-address): '*'; port: 3306
2014-05-13 13:36:12 8225 [Note] IPv6 is available.
2014-05-13 13:36:12 8225 [Note]  - '::' resolves to '::';
2014-05-13 13:36:12 8225 [Note] Server socket created on IP: '::'.
2014-05-13 13:36:12 8225 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-05-13 13:36:12 8225 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2014-05-13 13:36:12 8225 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2014-05-13 13:36:12 8225 [Note] Event Scheduler: Loaded 0 events
2014-05-13 13:36:12 8225 [Note] /Applications/AMPPS/mysql/bin/mysqld: ready for connections.
Version: '5.6.17-log'  socket: '/Applications/AMPPS/mysql/tmp/mysql.sock'  port: 3306  Source distribution

I have tried the following from this post and the other post mentioned:

1. adding innodb_force_recovery = 1 to config file
2. backup and move log files and mysql-bin files from /ampss/var
3. backup and move innodb files from /ampps/var/mysql