Reply to thread

Message

Some more information on debugging/logging MySQL: apparently you need a specific binary compiled with debug options turned on, which outputs to a file called mysql.trace. The debug version of mysqld.exe (the terminal 'd' stands for daemon ie server, not debug) is usually called mysqld-debug.exe but it isn't always available in the installer, and it isn't in the MP MySQL installer - I checked using LessMSI - so it doesn't get installed. I managed to find an zipped archived version of MySQL 5.1.38 which did have have a copy of mysqld-debug.exe (and two other mysqld-debug files with different extensions) (and running the file with --verbose --help did indeed confirm it was wired for debug) so I copied all three to the HTPC, modified the image path for the service and started the service, which started OK (but adding --debug made it conk out), but no mysql.trace. Checking the mysql.err log we've been using all along confirmed the debug version started, but was missing some freaking ?func(tions)... at which point I started losing the will to live again...

Bottom line I think is we are not going to get a mysql.trace, at least within a time frame of reasonable effot.

<blockquote data-quote="CathodeRay" data-source="post: 1148544" data-attributes="member: 128074">Some more information on debugging/logging MySQL: apparently you need a specific binary compiled with debug options turned on, which outputs to a file called mysql.trace. The debug version of mysqld.exe (the terminal 'd' stands for daemon ie server, not debug) is usually called mysqld-debug.exe but it isn't always available in the installer, and it isn't in the MP MySQL installer - I checked using LessMSI - so it doesn't get installed. I managed to find an zipped archived version of MySQL 5.1.38 which did have have a copy of mysqld-debug.exe (and two other mysqld-debug files with different extensions) (and running the file with --verbose --help did indeed confirm it was wired for debug) so I copied all three to the HTPC, modified the image path for the service and started the service, which started OK (but adding --debug made it conk out), but no mysql.trace. Checking the mysql.err log we've been using all along confirmed the debug version started, but was missing some freaking ?func(tions)... at which point I started losing the will to live again...Bottom line I think is we are not going to get a mysql.trace, at least within a time frame of reasonable effot.</blockquote>

[QUOTE="CathodeRay, post: 1148544, member: 128074"] Some more information on debugging/logging MySQL: apparently you need a specific binary compiled with debug options turned on, which outputs to a file called mysql.trace. The debug version of mysqld.exe (the terminal 'd' stands for daemon ie server, not debug) is usually called mysqld-debug.exe but it isn't always available in the installer, and it isn't in the MP MySQL installer - I checked using LessMSI - so it doesn't get installed. I managed to find an zipped archived version of MySQL 5.1.38 which did have have a copy of mysqld-debug.exe (and two other mysqld-debug files with different extensions) (and running the file with --verbose --help did indeed confirm it was wired for debug) so I copied all three to the HTPC, modified the image path for the service and started the service, which started OK (but adding --debug made it conk out), but no mysql.trace. Checking the mysql.err log we've been using all along confirmed the debug version started, but was missing some freaking ?func(tions)... at which point I started losing the will to live again... Bottom line I think is we are not going to get a mysql.trace, at least within a time frame of reasonable effot. [/QUOTE]