* [Bug translator/11504] New: Wrong location for inferred type conflict in error message
@ 2010-04-16 19:36 mjw at redhat dot com
2010-04-16 20:38 ` [Bug translator/11504] " chwang at redhat dot com
` (5 more replies)
0 siblings, 6 replies; 8+ messages in thread
From: mjw at redhat dot com @ 2010-04-16 19:36 UTC (permalink / raw)
To: systemtap
The following script will give a wrong location for the actual derived type
conflict:
probe nfs.aop.readpages {
printf("size=%d\n", size);
}
probe nfs.aop.readpages.return {
printf("size=%s\n", size);
}
$ stap -p2 t.stp
semantic error: probe_2472 with type mismatch (long vs. string): identifier
'size' at /usr/share/systemtap/tapset/nfs.stp:930:13
source: size = $return
^
semantic error: probe_2472 type first inferred here (string): identifier 'size'
at t.stp:2:22
source: printf("size=%d\n", size);
^
Pass 2: analysis failed. Try again with another '--vp 01' option.
The problem isn't on line 2, where size is used as a long, but on line 6 where
size is used as string.
--
Summary: Wrong location for inferred type conflict in error
message
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: mjw at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=11504
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug translator/11504] Wrong location for inferred type conflict in error message
2010-04-16 19:36 [Bug translator/11504] New: Wrong location for inferred type conflict in error message mjw at redhat dot com
@ 2010-04-16 20:38 ` chwang at redhat dot com
2010-04-17 14:27 ` chwang at redhat dot com
` (4 subsequent siblings)
5 siblings, 0 replies; 8+ messages in thread
From: chwang at redhat dot com @ 2010-04-16 20:38 UTC (permalink / raw)
To: systemtap
------- Additional Comments From chwang at redhat dot com 2010-04-16 16:43 -------
fwiw, it looks like typeresolutioninfo::mismatched in elaborate.cxx searches
resolved_toks for the first matching definition. The error should have been
thrown when parsing the second instance of size in the given script, but it
seems to have gotten thrown off because 'size' is not a locally declared global.
Instead of comparing (string) size to (global double) size it does the reverse.
I'll look for a way to unreverse it without breaking anything else.
Checking types might be a safe way to resolve this problem, but resolved_toks
don't have an exp_type to compare to.
-C
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11504
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug translator/11504] Wrong location for inferred type conflict in error message
2010-04-16 19:36 [Bug translator/11504] New: Wrong location for inferred type conflict in error message mjw at redhat dot com
2010-04-16 20:38 ` [Bug translator/11504] " chwang at redhat dot com
@ 2010-04-17 14:27 ` chwang at redhat dot com
2010-05-03 13:56 ` fche at redhat dot com
` (3 subsequent siblings)
5 siblings, 0 replies; 8+ messages in thread
From: chwang at redhat dot com @ 2010-04-17 14:27 UTC (permalink / raw)
To: systemtap
------- Additional Comments From chwang at redhat dot com 2010-04-16 19:36 -------
I was mistaken, size is not a global in nfs.stp. 'size' is a local parameter
taken from the probe point nfs.aop.readpages.{,return}.
I could fix this by giving tokens an exp_type attribute, or (hand-waving) some
sort of context-filtering to determine if two tokens are visible to each other.
Not all tokens can have a sensible exp_type.
On a side note, declaring size as global in nfs.stp gets rid of this problem.
Caveat: type mismatch with size as a global creates a longer error:
semantic error: probe_1978 with type mismatch (long vs. string): identifier
'size' at /usr/local/share/systemtap/tapset/nfs.stp:875:13
source: size = $return
^
semantic error: probe_1978 type first inferred here (string): identifier 'size'
at temp/11504.stp:2:22
source: printf("size=%s\n", size);
^
semantic error: probe_1980 with type mismatch (string vs. long): identifier
'nr_to_write' at /usr/local/share/systemtap/tapset/nfs.stp:1004:16
source: size = nr_to_write
^
semantic error: probe_1980 type first inferred here (long): identifier
'nr_to_write' at :996:9
source: nr_to_write = $wbc->nr_to_write
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11504
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug translator/11504] Wrong location for inferred type conflict in error message
2010-04-16 19:36 [Bug translator/11504] New: Wrong location for inferred type conflict in error message mjw at redhat dot com
2010-04-16 20:38 ` [Bug translator/11504] " chwang at redhat dot com
2010-04-17 14:27 ` chwang at redhat dot com
@ 2010-05-03 13:56 ` fche at redhat dot com
2010-05-06 0:13 ` chwang at redhat dot com
` (2 subsequent siblings)
5 siblings, 0 replies; 8+ messages in thread
From: fche at redhat dot com @ 2010-05-03 13:56 UTC (permalink / raw)
To: systemtap
------- Additional Comments From fche at redhat dot com 2010-04-30 18:00 -------
The typeresolution_info::mismatch routine, basing matches on the
token->content fields, seems too naive, and leads to junky stuff like:
stap -p2 -e 'probe begin { log(2 + "yo") }'
semantic error: probe_1971 uses invalid operator: operator '+' at <input>:1:21
source: probe begin { log(2 + "yo") }
^
semantic error: probe_1971 with type mismatch (string vs. long): string 'yo' at
:1:23
source: probe begin { log(2 + "yo") }
^
semantic error: probe_1971 with type mismatch (long vs. string): operator '+' at
:1:21
source: probe begin { log(2 + "yo") }
^
semantic error: probe_1971 type first inferred here (string): operator '+' at :1:21
source: probe begin { log(2 + "yo") }
^
semantic error: probe_1971 with type mismatch (long vs. string): identifier
'log' at :1:15
source: probe begin { log(2 + "yo") }
The core issue is that it is not tokens that get types, but expression objects.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11504
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug translator/11504] Wrong location for inferred type conflict in error message
2010-04-16 19:36 [Bug translator/11504] New: Wrong location for inferred type conflict in error message mjw at redhat dot com
` (2 preceding siblings ...)
2010-05-03 13:56 ` fche at redhat dot com
@ 2010-05-06 0:13 ` chwang at redhat dot com
2010-05-06 0:24 ` Kernel gpf & panic during make installcheck 1.2/0.137 David A Sperry
2010-05-10 17:48 ` [Bug translator/11504] Wrong location for inferred type conflict in error message fche at redhat dot com
2010-05-17 15:31 ` chwang at redhat dot com
5 siblings, 1 reply; 8+ messages in thread
From: chwang at redhat dot com @ 2010-05-06 0:13 UTC (permalink / raw)
To: systemtap
------- Additional Comments From chwang at redhat dot com 2010-05-04 19:19 -------
(In reply to comment #3)
> The typeresolution_info::mismatch routine, basing matches on the
> token->content fields, seems too naive, and leads to junky stuff like:
> The core issue is that it is not tokens that get types, but expression objects.
Should I add an exp_type to tokens? It wouldn't be used very often.
Alternatively, we could keep an array of resolved expression objects and use
that to check for mismatches?
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11504
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Kernel gpf & panic during make installcheck 1.2/0.137
2010-05-06 0:13 ` chwang at redhat dot com
@ 2010-05-06 0:24 ` David A Sperry
0 siblings, 0 replies; 8+ messages in thread
From: David A Sperry @ 2010-05-06 0:24 UTC (permalink / raw)
To: systemtap
Hi,
I'm trying to get systemtap tor work with RedHat MRG had a number of
difficulties with hangs and panics.
The target system is running RHEL5.4 with the latest MRG real-time kernel
2.6.24.7-149
The snapshot of systemtap is 1.2/0.137
Here's the error message
Running /root/build/systemtap-1.2/testsuite/systemtap.base/kprobes.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/kretprobe-vars.exp ...
Message from syslogd@ at Wed May 5 10:13:57 2010 ...
jmeevm34 kernel: general protection fault: 0000 [1] PREEMPT SMP
Message from syslogd@ at Wed May 5 10:13:57 2010 ...
jmeevm34 kernel: Code: 39 47 30 55 8b b7 0c 08 00 00 89 c2 0f 4e 57 30 48
89 e5 31 c9 eb 1e 48 63 c1 48 6b c0 28 48 8b 84 38 10 08 00 00 48 85 c0 74
08 <8b> 40 50 39 c2 0f 4f d0 ff c1 39 f1 7c de 48 8d 87 f0 07 00 00
Message from syslogd@ at Wed May 5 10:13:57 2010 ...
jmeevm34 kernel: Kernel panic - not syncing: Fatal exception
Any thoughts on what to try next?
Thanks,
Dave
Here are snips of the test and /var/log/messages:
[root@jmeevm34 systemtap-1.2]# make installcheck
if test \! -e /root/systemtap-1.2-4487/bin/stap; then \
echo /root/systemtap-1.2-4487/bin/stap doesn\'t exist, run make
install; \
exit -1; \
fi; \
if test ./stap -nt /root/systemtap-1.2-4487/bin/stap; then \
echo "/root/systemtap-1.2-4487/bin/stap is not recent, run make
install"; \
exit -1; \
fi;
make -C testsuite installcheck RUNTESTFLAGS=""
make[1]: Entering directory `/root/build/systemtap-1.2/testsuite'
make check-DEJAGNU RUNTESTFLAGS=" --tool_opts \'install \'"
make[2]: Entering directory `/root/build/systemtap-1.2/testsuite'
srcdir=`CDPATH="${ZSH_VERSION+.}:" && cd . && pwd`; export srcdir; \
EXPECT=expect; export EXPECT; \
runtest="env SYSTEMTAP_TESTAPPS=
SYSTEMTAP_RUNTIME=/root/systemtap-1.2-4487/share/systemtap/runtime
SYSTEMTAP_TAPSET=/root/systemtap-1.2-4487/share/systemtap/tapset
LD_LIBRARY_PATH=/root/systemtap-1.2-4487/lib/systemtap
CRASH_LIBDIR=/root/systemtap-1.2-4487/lib/systemtap
PATH=/root/systemtap-1.2-4487/bin:$PATH
SYSTEMTAP_PATH=/root/systemtap-1.2-4487/bin
SYSTEMTAP_INCLUDES=/root/systemtap-1.2-4487/include
PKGLIBDIR=/root/systemtap-1.2-4487/libexec/systemtap ./execrc runtest"; \
if /bin/sh -c "$runtest --version" > /dev/null 2>&1; then \
exit_status=0; l='systemtap'; for tool in $l; do \
if $runtest --tool $tool --tool_opts \'\' --srcdir $srcdir
--tool_opts \'install \'; \
then :; else exit_status=1; fi; \
done; \
else echo "WARNING: could not find \`runtest'" 1>&2; :;\
fi; \
exit $exit_status
WARNING: Couldn't find the global config file.
kernel location: /usr/lib/debug/lib/modules/2.6.24.7-149/vmlinux
kernel version: 2.6.24.7-149
systemtap location: /root/systemtap-1.2-4487/bin/stap
systemtap version: version 1.2/0.137 non-git sources
gcc location: /usr/bin/gcc
gcc version: gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-46)
Test Run By root on Wed May 5 10:10:23 2010
Native configuration is x86_64-redhat-linux-gnu
=== systemtap tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for
target.
Using /root/build/systemtap-1.2/testsuite/config/unix.exp as
tool-and-target-specific interface file.
Host: Linux jmeevm34 2.6.24.7-149 #1 SMP PREEMPT RT Wed May 5 09:02:04 EDT
2010 x86_64 x86_64 x86_64 GNU/Linux
Snapshot: version 1.2/0.137 non-git sources
GCC: 4.1.2 [gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-46)]
Distro: Red Hat Enterprise Linux Server release 5.4 (Tikanga)
Running /root/build/systemtap-1.2/testsuite/systemtap/notest.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.apps/mysql.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.apps/postgres.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.apps/tcl.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.apps/xulrunner.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/add.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/alias-condition.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/alias_tapset.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/alternatives.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/arith.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/arith_limits.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/array_size.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/array_string.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/atomic.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/backtrace.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/badkprobe.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/be_order.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/beginenderror.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/bench.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/bitfield.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/bz10078.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/bz5274.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/bz6850.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/cache.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/cast.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/cmd_parse.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/const_value.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/control_limits.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/crash.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/ctime.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/cu-decl.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/cxxclass.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/debugpath.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/deref.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/deref2.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/div0.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/dtrace.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/equal.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/error_fn.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/externalvar.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/finloop2.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/flightrec1.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/flightrec2.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/flightrec3.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/flightrec4.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/flightrec5.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/global_end.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/global_init.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/global_stat.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/global_vars.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/gtod.exp ...
FAIL: gtod (96)
Running /root/build/systemtap-1.2/testsuite/systemtap.base/if.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/inc.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/inlinedvars.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/itrace.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/kfunct.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/kmodule.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/kprobes.exp ...
Running /root/build/systemtap-1.2/testsuite/systemtap.base/kretprobe-vars.exp ...
Message from syslogd@ at Wed May 5 10:13:57 2010 ...
jmeevm34 kernel: general protection fault: 0000 [1] PREEMPT SMP
Message from syslogd@ at Wed May 5 10:13:57 2010 ...
jmeevm34 kernel: Code: 39 47 30 55 8b b7 0c 08 00 00 89 c2 0f 4e 57 30 48
89 e5 31 c9 eb 1e 48 63 c1 48 6b c0 28 48 8b 84 38 10 08 00 00 48 85 c0 74
08 <8b> 40 50 39 c2 0f 4f d0 ff c1 39 f1 7c de 48 8d 87 f0 07 00 00
Message from syslogd@ at Wed May 5 10:13:57 2010 ...
jmeevm34 kernel: Kernel panic - not syncing: Fatal exception
**********************************************************************************
/var/log/messages
May 5 10:11:28 jmeevm34 ntpd[2822]: synchronized to LOCAL(0), stratum 10
May 5 10:11:28 jmeevm34 ntpd[2822]: kernel time sync enabled 0001
May 5 10:13:57 jmeevm34 kernel: WARNING: at kernel/rtmutex.c:1311
try_to_take_rw_read()
May 5 10:13:57 jmeevm34 kernel: Pid: 17659, comm: stapio Not tainted
2.6.24.7-149 #1
May 5 10:13:57 jmeevm34 kernel:
May 5 10:13:57 jmeevm34 kernel: Call Trace:
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8105f3c6>] try_to_take_rw_read
+0x48f/0x5a8
May 5 10:13:57 jmeevm34 kernel: [<ffffffff81060281>] rt_read_slowtrylock
+0x5e/0x7b
May 5 10:13:57 jmeevm34 kernel: [<ffffffff81289ac7>]
rt_mutex_down_read_trylock+0xe/0x10
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128b357>] rt_read_trylock
+0x9/0xb
May 5 10:13:57 jmeevm34 kernel:
[<ffffffff882b2bc9>] :stap_1958e27087240ee628f291b0a0478dc0_8495:stp_lock_probe
+0x76/0xa3
May 5 10:13:57 jmeevm34 kernel: [<ffffffff810265fd>] ?
kretprobe_trampoline+0x1/0x4
May 5 10:13:57 jmeevm34 kernel:
[<ffffffff882b74ce>] :stap_1958e27087240ee628f291b0a0478dc0_8495:probe_1977
+0x25/0xf9f
May 5 10:13:57 jmeevm34 kernel: [<ffffffff810265fd>] ?
kretprobe_trampoline+0x1/0x4
May 5 10:13:57 jmeevm34 kernel:
[<ffffffff882b5e9a>] :stap_1958e27087240ee628f291b0a0478dc0_8495:enter_kretprobe_probe
+0x1c1/0x31d
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128d0a4>]
trampoline_probe_handler+0x5d/0x156
May 5 10:13:57 jmeevm34 kernel: [<ffffffff810265fc>] ?
kretprobe_trampoline+0x0/0x4
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128ce96>] kprobe_handler
+0x1b2/0x1f4
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128cf07>]
kprobe_exceptions_notify+0x2f/0x73
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128daf1>] notifier_call_chain
+0x33/0x5b
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128db56>]
__atomic_notifier_call_chain+0x3d/0x53
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128db7b>]
atomic_notifier_call_chain+0xf/0x11
May 5 10:13:57 jmeevm34 kernel: [<ffffffff81056ea4>] notify_die+0x2e/0x30
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128c501>] do_int3+0x32/0x71
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128be0f>] int3+0x7f/0x90
May 5 10:13:57 jmeevm34 kernel: [<ffffffff810b1d21>] ? sys_read+0x4a/0x75
May 5 10:13:57 jmeevm34 kernel: [<ffffffff810265fc>] ?
kretprobe_trampoline+0x0/0x4
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8100c3be>] traceret+0x0/0x5
May 5 10:13:57 jmeevm34 kernel:
May 5 10:13:57 jmeevm34 kernel: WARNING: at kernel/rtmutex.c:1704
rt_read_slowunlock()
May 5 10:13:57 jmeevm34 kernel: Pid: 17659, comm: stapio Not tainted
2.6.24.7-149 #1
May 5 10:13:57 jmeevm34 kernel:
May 5 10:13:57 jmeevm34 kernel: Call Trace:
May 5 10:13:57 jmeevm34 kernel: [<ffffffff81289e29>] rt_read_slowunlock
+0x1f9/0x4a6
May 5 10:13:57 jmeevm34 kernel: [<ffffffff810601ff>]
rt_rwlock_read_unlock+0x9a/0x9e
May 5 10:13:57 jmeevm34 kernel:
[<ffffffff882b24ec>] ? :stap_1958e27087240ee628f291b0a0478dc0_8495:hash_iii
+0x1a/0x22
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128b36d>] rt_read_unlock
+0x9/0xb
May 5 10:13:57 jmeevm34 kernel:
[<ffffffff882b2b4c>] :stap_1958e27087240ee628f291b0a0478dc0_8495:stp_unlock_probe
+0x35/0x3c
May 5 10:13:57 jmeevm34 kernel:
[<ffffffff882b7d6f>] :stap_1958e27087240ee628f291b0a0478dc0_8495:probe_1977
+0x8c6/0xf9f
May 5 10:13:57 jmeevm34 kernel: [<ffffffff810265fd>] ?
kretprobe_trampoline+0x1/0x4
May 5 10:13:57 jmeevm34 kernel:
[<ffffffff882b5e9a>] :stap_1958e27087240ee628f291b0a0478dc0_8495:enter_kretprobe_probe
+0x1c1/0x31d
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128d0a4>]
trampoline_probe_handler+0x5d/0x156
May 5 10:13:57 jmeevm34 kernel: [<ffffffff810265fc>] ?
kretprobe_trampoline+0x0/0x4
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128ce96>] kprobe_handler
+0x1b2/0x1f4
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128cf07>]
kprobe_exceptions_notify+0x2f/0x73
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128daf1>] notifier_call_chain
+0x33/0x5b
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128db56>]
__atomic_notifier_call_chain+0x3d/0x53
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128db7b>]
atomic_notifier_call_chain+0xf/0x11
May 5 10:13:57 jmeevm34 kernel: [<ffffffff81056ea4>] notify_die+0x2e/0x30
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128c501>] do_int3+0x32/0x71
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128be0f>] int3+0x7f/0x90
May 5 10:13:57 jmeevm34 kernel: [<ffffffff810b1d21>] ? sys_read+0x4a/0x75
May 5 10:13:57 jmeevm34 kernel: [<ffffffff810265fc>] ?
kretprobe_trampoline+0x0/0x4
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8100c3be>] traceret+0x0/0x5
May 5 10:13:57 jmeevm34 kernel:
May 5 10:13:57 jmeevm34 kernel: general protection fault: 0000 [1] PREEMPT
SMP
May 5 10:13:57 jmeevm34 kernel: CPU 1
May 5 10:13:57 jmeevm34 kernel: Modules linked in:
stap_1958e27087240ee628f291b0a0478dc0_8495 nfsd auth_rpcgss exportfs
i2c_dev i2c_core nfs nfs_acl lockd sunrpc dm_multipath scsi_dh video output
sbs sbshc battery ac ipv6 parport_pc lp parport floppy sg serio_raw sr_mod
button cdrom 8139too 8139cp pcspkr mii dm_snapshot dm_zero dm_mirror dm_mod
pata_acpi ata_piix ata_generic libata sd_mod scsi_mod ext3 jbd mbcache
uhci_hcd ohci_hcd ehci_hcd
May 5 10:13:57 jmeevm34 kernel: Pid: 17673, comm: cat Not tainted
2.6.24.7-149 #1
May 5 10:13:57 jmeevm34 kernel: RIP: 0010:[<ffffffff8105ebb8>]
[<ffffffff8105ebb8>] rt_mutex_getprio+0x2e/0x5f
May 5 10:13:57 jmeevm34 kernel: RSP: 0000:ffff8100be5afd98 EFLAGS:
00010086
May 5 10:13:57 jmeevm34 kernel: RAX: a841a842a841a841 RBX:
ffff8101101ee3c0 RCX: 000000000000006e
May 5 10:13:57 jmeevm34 kernel: RDX: 0000000000000000 RSI:
000000000000006f RDI: ffff8101101ee3c0
May 5 10:13:57 jmeevm34 kernel: RBP: ffff8100be5afd98 R08:
ffffe2000444acd0 R09: 0000000000000000
May 5 10:13:57 jmeevm34 kernel: R10: 0000003e4c003a88 R11:
0000004400000002 R12: 0000000000000292
May 5 10:13:57 jmeevm34 kernel: R13: ffff8101101eeb98 R14:
0000000000000001 R15: 0000000000000000
May 5 10:13:57 jmeevm34 kernel: FS: 00007ffb825466e0(0000)
GS:ffff810139ae9b40(0000) knlGS:0000000000000000
May 5 10:13:57 jmeevm34 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
000000008005003b
May 5 10:13:57 jmeevm34 kernel: CR2: 0000003e4c005006 CR3:
00000000bf91c000 CR4: 00000000000006e0
May 5 10:13:57 jmeevm34 kernel: DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
May 5 10:13:57 jmeevm34 kernel: DR3: 0000000000000000 DR6:
00000000ffff0ff0 DR7: 0000000000000400
May 5 10:13:57 jmeevm34 kernel: Process cat (pid: 17673, threadinfo
ffff8100be5ae000, task ffff8101101ee3c0)
May 5 10:13:57 jmeevm34 kernel: Stack: ffff8100be5afdb8 ffffffff8105ef24
ffff8100be5afdc8 ffff8101101ee3c0
May 5 10:13:57 jmeevm34 kernel: ffff8100be5afde8 ffffffff8105f81e
ffff8100b7930028 0000000000000000
May 5 10:13:57 jmeevm34 kernel: ffff8101034c2120 00000000ffffffff
ffff8100be5afe38 ffffffff8128a09d
May 5 10:13:57 jmeevm34 kernel: Call Trace:
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8105ef24>]
__rt_mutex_adjust_prio+0x11/0x24
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8105f81e>] rt_mutex_adjust_prio
+0x2a/0x3e
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128a09d>] rt_read_slowunlock
+0x46d/0x4a6
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8106040e>] rt_mutex_up_read
+0x9d/0xa1
May 5 10:13:57 jmeevm34 kernel: [<ffffffff81060aa5>] rt_up_read+0x9/0xb
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128d747>] do_page_fault
+0x3f6/0x76d
May 5 10:13:57 jmeevm34 kernel: [<ffffffff81078a66>] ? audit_syscall_exit
+0x309/0x328
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128bb19>] error_exit+0x0/0x51
May 5 10:13:57 jmeevm34 kernel:
May 5 10:13:57 jmeevm34 kernel:
May 5 10:13:57 jmeevm34 kernel: Code: 39 47 30 55 8b b7 0c 08 00 00 89 c2
0f 4e 57 30 48 89 e5 31 c9 eb 1e 48 63 c1 48 6b c0 28 48 8b 84 38 10 08 00
00 48 85 c0 74 08 <8b> 40 50 39 c2 0f 4f d0 ff c1 39 f1 7c de 48 8d 87 f0
07 00 00
May 5 10:13:57 jmeevm34 kernel: RIP [<ffffffff8105ebb8>] rt_mutex_getprio
+0x2e/0x5f
May 5 10:13:57 jmeevm34 kernel: RSP <ffff8100be5afd98>
May 5 10:13:57 jmeevm34 kernel: Kernel panic - not syncing: Fatal
exception
May 5 10:13:57 jmeevm34 kernel: Pid: 17673, comm: cat Tainted: G D
2.6.24.7-149 #1
May 5 10:13:57 jmeevm34 kernel:
May 5 10:13:57 jmeevm34 kernel: Call Trace:
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8103dc64>] panic+0xaf/0x160
May 5 10:13:57 jmeevm34 kernel: [<ffffffff810303a9>] ? __wake_up_common
+0x41/0x74
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8103a9d8>] ? __wake_up
+0x3a/0x5b
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8103e00f>] ? wake_up_klogd
+0x32/0x34
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128be8b>] oops_end+0x54/0x5d
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8100dbdd>] die+0x4a/0x54
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128c4c6>]
do_general_protection+0x111/0x11a
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128bb19>] error_exit+0x0/0x51
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8105ebb8>] ? rt_mutex_getprio
+0x2e/0x5f
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8105ef24>] ?
__rt_mutex_adjust_prio+0x11/0x24
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8105f81e>] ?
rt_mutex_adjust_prio+0x2a/0x3e
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128a09d>] ? rt_read_slowunlock
+0x46d/0x4a6
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8106040e>] ? rt_mutex_up_read
+0x9d/0xa1
May 5 10:13:57 jmeevm34 kernel: [<ffffffff81060aa5>] ? rt_up_read+0x9/0xb
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128d747>] ? do_page_fault
+0x3f6/0x76d
May 5 10:13:57 jmeevm34 kernel: [<ffffffff81078a66>] ? audit_syscall_exit
+0x309/0x328
May 5 10:13:57 jmeevm34 kernel: [<ffffffff8128bb19>] ? error_exit
+0x0/0x51
May 5 10:13:57 jmeevm34 kernel:
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug translator/11504] Wrong location for inferred type conflict in error message
2010-04-16 19:36 [Bug translator/11504] New: Wrong location for inferred type conflict in error message mjw at redhat dot com
` (3 preceding siblings ...)
2010-05-06 0:13 ` chwang at redhat dot com
@ 2010-05-10 17:48 ` fche at redhat dot com
2010-05-17 15:31 ` chwang at redhat dot com
5 siblings, 0 replies; 8+ messages in thread
From: fche at redhat dot com @ 2010-05-10 17:48 UTC (permalink / raw)
To: systemtap
------- Additional Comments From fche at redhat dot com 2010-05-10 14:33 -------
(In reply to comment #4)
> (In reply to comment #3)
> > The typeresolution_info::mismatch routine, basing matches on the
> > token->content fields, seems too naive, and leads to junky stuff like:
> > The core issue is that it is not tokens that get types, but expression objects.
>
> Should I add an exp_type to tokens? It wouldn't be used very often.
No, that would not make sense.
> Alternatively, we could keep an array of resolved expression objects and use
> that to check for mismatches?
That would make much more sense. Try passing/storing expression* and/or
symbol* instead of token*'s to the various resolved/invalid/mismatch()
family of functions.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11504
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug translator/11504] Wrong location for inferred type conflict in error message
2010-04-16 19:36 [Bug translator/11504] New: Wrong location for inferred type conflict in error message mjw at redhat dot com
` (4 preceding siblings ...)
2010-05-10 17:48 ` [Bug translator/11504] Wrong location for inferred type conflict in error message fche at redhat dot com
@ 2010-05-17 15:31 ` chwang at redhat dot com
5 siblings, 0 replies; 8+ messages in thread
From: chwang at redhat dot com @ 2010-05-17 15:31 UTC (permalink / raw)
To: systemtap
------- Additional Comments From chwang at redhat dot com 2010-05-14 19:16 -------
Created an attachment (id=4793)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=4793&action=view)
Patch for 11504
Attempt #2. Very minor hack to keep an exp_type* vector that's updated whenever
the tokens vector is updated. This appears to fix the problem, though I don't
know if it is efficient enough.
Attempt #1 (not attached) was passing expression to
typeresolution_info::resolved, which failed because I couldn't get an
expression* from the Referrer/Referent templates in
elaborate.cxx:resolve_2types.
I will try getting the exp_type from symbol* as well, if this patch is not
acceptable.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11504
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2010-05-14 19:16 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-04-16 19:36 [Bug translator/11504] New: Wrong location for inferred type conflict in error message mjw at redhat dot com
2010-04-16 20:38 ` [Bug translator/11504] " chwang at redhat dot com
2010-04-17 14:27 ` chwang at redhat dot com
2010-05-03 13:56 ` fche at redhat dot com
2010-05-06 0:13 ` chwang at redhat dot com
2010-05-06 0:24 ` Kernel gpf & panic during make installcheck 1.2/0.137 David A Sperry
2010-05-10 17:48 ` [Bug translator/11504] Wrong location for inferred type conflict in error message fche at redhat dot com
2010-05-17 15:31 ` chwang at redhat dot com
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).