Re: Running MySQL server in debug mode

[Amit k. Saha]

On Thu, Jun 19, 2008 at 2:08 PM, Guilhem Bichot <guilhem@stripped> wrote:
> Hi,
>
> On Thu, Jun 19, 2008 at 11:18:44AM +0530, Amit k. Saha wrote:
>> On Wed, Jun 18, 2008 at 5:41 PM, Amit k. Saha <amitsaha.in@stripped>
> wrote:
>> > On Wed, Jun 18, 2008 at 4:06 PM, Amit k. Saha <amitsaha.in@stripped>
> wrote:
>> >> Hello all,
>> >>
>> >> I did this:  ./mysqld --debug, a couple of times to start the server
>> >> in debug mode,  and worked fine (started showing me a trace, etc).
>> >> However, it isn't working anymore. This is all I get:
>> >>
>> >> 080618 16:05:52 [Note] Event Scheduler: Loaded 0 events
>> >> 080618 16:05:52 [Note] ./mysqld: ready for connections.
>> >> Version: '5.1.24-rc-debug'  socket: '/tmp/mysql.sock'  port: 3306
>> >> Source distribution
>> >> .
>> >
>> >
>> > Some more info:
>> >
>> > The trace is stored in /tmp/mysqld.trace  but no screen dump.
>>
>> I get a screen dump when I use a DBUG control string such as:
>>
>> ./mysqld --debug=d:t:F:L,
>>
>> but no /tmp/mysqld.trace
>>
>> But, is the other way round when I do not use *any* control string.
>>
>> I have tried using  ./mysqld --debug=d:t:F:L:N, \\ mysld.trace
>> as a guess work, but doesn't help
>
> To get output to a file, add o,the_file_name, like this:
> --debug=d:t:F:L:o,the_file_name
> (it's all explained in dbug/user.ps).
> When you use just --debug, mysqld uses a default value for the control
> string, which can be found in sql/mysqld.cc and is:
> d:t:i:o,/tmp/mysqld.trace

Thanks! That does it.

>
> I'll send you in private a copy of user.ps.

I needed it!


-- 
Amit Kumar Saha
http://blogs.sun.com/amitsaha/
http://amitksaha.blogspot.com