Bug #33554 mabackup run by launchd exits abnormally with a bus error
Submitted: 28 Dec 2007 14:58 Modified: 15 Jan 2008 6:01
Reporter: Robbie Bible Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.2.12 OS:MacOS
Assigned to: CPU Architecture:Any
Tags: launchd, mabackup, SIGBUS

[28 Dec 2007 14:58] Robbie Bible 
Description:
MySQL Administrator dump v1.4
MySQL Server v5.0.45-log
MySQL Client v5.1.8
Mac OS X Server v10.5.1 on a 64-bit Xserve

If mabackup is started by launchd, it exits abnormally with a bus error.  Running mabackup from Terminal with the same parameters as the launchd job does not generate a bus error, and the backup file created in both instances is identical.

How to repeat:
Start mabackup via launchd.
[28 Dec 2007 15:00] Robbie Bible 
launchd plist for the backup job

Attachment: com.infomart.FlysprayBackup.plist (, text), 655 bytes.
[15 Jan 2008 6:01] Sveta Smirnova 
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicate of bug #28408