In the last episode (Sep 26), Ian Monroe said: > On Fri, Sep 26, 2008 at 1:55 PM, Ian Monroe <[EMAIL PROTECTED]> wrote: > > On Fri, Sep 26, 2008 at 9:37 AM, Ian Monroe <[EMAIL PROTECTED]> wrote: > >> So we're using MySQL Embedded in Amarok, it works fine for most of us > >> that use 5.1, including myself. However the following backtrace is > >> from the second person to have this issue. Its repeatable, happens at > >> startup. > >> > >> Is there something about how their MySQL is setup on their system that > >> could cause such a crash? > > [snip] > >> mysql_library_init(num_elements, server_options, server_groups); > >> m_db = mysql_init(NULL); // <- crash happens HERE > > > > So we did figure out that mysql_library_init is returning 1, which > > explains why mysql_init is crashing. > > > > But how do we figure out what exactly the '1' means? Any clues? > > We figured it out: we had --skip-innodb, which crashed anyone who > didn't have Innodb support built. > > Is there any way we could have it add --skip-innodb if and only if > Innodb support is present? I can't find a mysql_* function that > describes server functionality. A compile time option would work as > well I suppose, since we're currently statically linking.
You want --loose-skip-innodb. http://dev.mysql.com/doc/refman/5.0/en/command-line-options.html If an option is prefixed by --loose, a program does not exit with an error if it does not recognize the option, but instead issues only a warning: $ mysql --loose-no-such-option mysql: WARNING: unknown option '--no-such-option' -- Dan Nelson [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
