List:Internals« Previous MessageNext Message »
From:Sasha Pachev Date:October 1 2001 1:27pm
Subject:Re: mysqld.trace troubles
View as plain text  
On Sunday 30 September 2001 23:42, Alexander Belkin wrote:
> On Sun, Sep 30, 2001 at 10:22:24PM +0300, Michael Widenius wrote:
> > 
> > Hi!
> > 
> > >>>>> "Alexander" == Alexander Belkin <bell@stripped>
> writes:
> > 
> > Alexander> Hi!
> > Alexander> After thread recive SIGSEGV, in mysqld.trace no any records, 
that writed
> > Alexander> before Segmentation Fault. This problem not caused by buffered 
output (i
> > Alexander> already try to make _db_fp_ unbuffered, may be in wrong way?).
> > 
> > To get unbuffered output in the trace file, use the 'O' for the
> > filename:
> > 
> > mysqld --debug=d:t:i:O,/tmp/ysqld.trace"
> 
> Yes. I do this. But i'am stupid. I try run mysqld under mysqld_safe, and
> when it restart mysqld, mysqld.trace was rewrited...

Alexander ( or do you go by Sasha?):

Here is the way I debug MySQL:

 * cd mysql-test
 * write a test case in t/testname.test
 * ./mysql-test-run --local --gdb testname

This will pop-up an xterm with gdb pre-loaded - all you need to do is set 
your breakpoints (if you need any), type "run", and then hit enter in the 
main window. After I push my change ( once 4.0.0 is out), you will not have 
to hit enter in the main window any more - everything will happen 
auto-magically.

 
-- 
MySQL Development Team
For technical support contracts, visit https://order.mysql.com/
   __  ___     ___ ____  __ 
  /  |/  /_ __/ __/ __ \/ /   Sasha Pachev <sasha@stripped>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, http://www.mysql.com/
/_/  /_/\_, /___/\___\_\___/  Provo, Utah, USA
       <___/                  
Thread
mysqld.trace troublesAlexander Belkin30 Sep
  • mysqld.trace troublesMichael Widenius30 Sep
    • Re: mysqld.trace troublesAlexander Belkin1 Oct
      • Re: mysqld.trace troublesSasha Pachev1 Oct