From: "Stone, Joshua I" <joshua.i.stone@intel.com>
To: "Hien Nguyen" <hien@us.ibm.com>
Cc: "SystemTAP" <systemtap@sources.redhat.com>,
"Nguyen, Thang P" <thang.p.nguyen@intel.com>
Subject: RE: nightly test result of systemtap in ppc64
Date: Tue, 09 May 2006 18:46:00 -0000 [thread overview]
Message-ID: <CBDB88BFD06F7F408399DBCF8776B3DC07281290@scsmsx403.amr.corp.intel.com> (raw)
I committed a fix - please see if it works for you now.
Josh
On Tuesday, May 09, 2006 11:30 AM, Hien Nguyen wrote:
> Stone, Joshua I wrote:
>
>> On Tuesday, May 09, 2006 11:02 AM, Hien Nguyen wrote:
>>
>>
>>> I initialized *ptr=NULL to get pass the compiler.
>>>
>>>
>>
>> Sure, but I would like to know why that error was reported in the
>> first place. As far as I can see, there's no way for 'ptr' to be
>> used uninitialized. If I'm missing something, then your fix just
>> means that we'll induce a NULL dereference if there's a problem.
>>
>>
>> Josh
>>
>>
> Here it is
> 46121 void function_probefunc (struct context* __restrict__ c) {
> 46122 struct function_probefunc_locals * __restrict__ l =
> 46123 & c->locals[c->nesting].function_probefunc;
> 46124 (void) l;
> 46125 #define CONTEXT c
> 46126 #define THIS l
> 46127 if (0) goto out;
> 46128 l->__retvalue[0] = '\0';
> 46129 {
> 46130 /* pure */
> 46131 char *dst, *ptr, *start;
> 46132 String str;
> 46133 int len = MAXSTRINGLEN;
> 46134
> 46135 start = strstr(CONTEXT->probe_point, "function(\"");
> 46136 if (start) {
> 46137 ptr = start + 10;
> 46138 } else {
> 46139 start = strstr(CONTEXT->probe_point,
> "inline(\""); 46140 if (start) {
> 46141 ptr = start + 8;
> 46142 }
> 46143 }
> 46144 if (start) {
> 46145 dst = THIS->__retvalue;
> 46146 while (*ptr != '@' && --len > 0 && *ptr)
> 46147 *dst++ = *ptr++;
> 46148 *dst = 0;
> 46149 goto out;
> 46150 }
> 46151 if (CONTEXT->regs) {
> 46152 str = _stp_string_init (0);
> 46153 _stp_symbol_sprint(str,
> REG_IP(CONTEXT->regs)); 46154 start =
> strstr(_stp_string_ptr(str), " : "); 46155 if
> (start) { 46156 dst = THIS->__retvalue;
> 46157 ptr = start+3;
> 46158 while (*ptr != '+' && --len > 0 &&
> *ptr) 46159 *dst++ = *ptr++;
> 46160 *dst = 0;
> 46161 }
> 46162 else {
> 46163 strlcpy(THIS->__retvalue,
> _stp_string_ptr(str),M AXSTRINGLEN);
> 46164 }
> 46165 goto out;
> 46166 }
> 46167 THIS->__retvalue[0] = '\0';
> 46168
> 46169 }
next reply other threads:[~2006-05-09 18:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 18:46 Stone, Joshua I [this message]
2006-05-10 16:19 ` Hien Nguyen
-- strict thread matches above, loose matches on Subject: below --
2006-05-15 20:44 Hien Nguyen
2006-05-09 18:19 Stone, Joshua I
2006-05-09 18:29 ` Hien Nguyen
2006-05-09 17:59 Stone, Joshua I
2006-05-09 18:02 ` Hien Nguyen
2006-05-09 17:28 Hien Nguyen
2006-04-24 18:16 Nightly " Hien Nguyen
2006-04-24 18:55 ` Frank Ch. Eigler
2006-04-24 22:18 ` Hien Nguyen
2006-05-01 21:53 ` Hien Nguyen
[not found] ` <20060503021650.GC11017@redhat.com>
[not found] ` <4458FFA2.3090802@us.ibm.com>
2006-05-07 22:52 ` Frank Ch. Eigler
2006-04-10 18:30 nightly " Hien Nguyen
2006-04-10 20:19 ` Hien Nguyen
2006-04-10 20:28 ` Roland McGrath
2006-04-10 20:42 ` Frank Ch. Eigler
2006-04-10 20:53 ` Roland McGrath
2006-04-10 21:05 ` Martin Hunt
2006-03-27 19:35 Nightly " Hien Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CBDB88BFD06F7F408399DBCF8776B3DC07281290@scsmsx403.amr.corp.intel.com \
--to=joshua.i.stone@intel.com \
--cc=hien@us.ibm.com \
--cc=systemtap@sources.redhat.com \
--cc=thang.p.nguyen@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).