From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11869 invoked by alias); 3 Apr 2006 03:43:49 -0000 Received: (qmail 11858 invoked by uid 48); 3 Apr 2006 03:43:47 -0000 Date: Mon, 03 Apr 2006 03:43:00 -0000 Message-ID: <20060403034347.11857.qmail@sourceware.org> From: "guanglei at cn dot ibm dot com" To: systemtap@sources.redhat.com In-Reply-To: <20060330093952.2497.guanglei@cn.ibm.com> References: <20060330093952.2497.guanglei@cn.ibm.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug runtime/2497] STP_STRING_SIZE set by stap is too small X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2006-q2/txt/msg00006.txt.bz2 ------- Additional Comments From guanglei at cn dot ibm dot com 2006-04-03 03:43 ------- (In reply to comment #7) > > If you use print_backtrace() it writes the output directly to stdout so there is > no limit. EXCEPT I see the ppc64 __stp_stack_sprint() function has put an > incorrect limit there. Perhaps that is the real problem you are trying to fix? > > If you want to fix that function, consider that if "str == _stp_stdout" then the > output is going to the output buffer, not a string of size STP_STRING_SIZE. > Up to now, print_backtrace() works well for me and will give a complete backtrace. I can call print_backtrace() to print the backtrace, but in fact I want to combine the string of backtrace with other information to generate the output of a specific event, like the following: String str = _stp_string_init (0); _stp_stack_sprint (str, CONTEXT->regs, 0); _lket_trace(THIS->var_id, "%1b%4b%1b%ld%4b%4b%s", cmd->device->sdev_state, scsi_info, cmd->sc_data_direction, cmd->request_buffer, cmd->request_bufflen, cmd->device->host->cmd_pid, _stp_string_ptr(str)); So what I want is a larger String obtained by _stp_string_init, while keep all other strings used by stap the same as before. -- http://sourceware.org/bugzilla/show_bug.cgi?id=2497 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.