1berry/MariaDB-server
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Silly mistake in gdb output: replaced print with resfile_print,

Browse Source 
but the latter only takes one argument, duh!
Fixed by concatenating the args (replace , with .)
This commit is contained in:
Bjorn Munch 2011-10-05 15:16:20 +02:00
parent dc265dc4a1
commit 83f3aa148b
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
mysql-test/lib/My/CoreDump.pm
View File

@ -81,7 +81,7 @@ sub _gdb {
return if $? >> 8; return if $? >> 8;
return unless $gdb_output; return unless $gdb_output;
resfile_print <<EOF, $gdb_output, "\n"; resfile_print <<EOF . $gdb_output . "\n";
Output from gdb follows. The first stack trace is from the failing thread. Output from gdb follows. The first stack trace is from the failing thread.
The following stack traces are from all threads (so the failing one is The following stack traces are from all threads (so the failing one is
duplicated). duplicated).
@ -245,7 +245,7 @@ sub _cdb {
$cdb_output=~ s/^Child\-SP RetAddr Call Site//gm; $cdb_output=~ s/^Child\-SP RetAddr Call Site//gm;
$cdb_output=~ s/\+0x([0-9a-fA-F]+)//gm; $cdb_output=~ s/\+0x([0-9a-fA-F]+)//gm;
resfile_print <<EOF, $cdb_output, "\n"; resfile_print <<EOF . $cdb_output . "\n";
Output from cdb follows. Faulting thread is printed twice,with and without function parameters Output from cdb follows. Faulting thread is printed twice,with and without function parameters
Search for STACK_TEXT to see the stack trace of Search for STACK_TEXT to see the stack trace of
the faulting thread. Callstacks of other threads are printed after it. the faulting thread. Callstacks of other threads are printed after it.