After building and bfu''in the lastest ON build, any time I run a dtrace
script I get a Seg Fault. Is there a dtrace for dtrace :)
Doug
root at prae> dtrace -n ''syscall::open*:entry { printf("%s
%s",execname,copyinstr(arg0)); }''
Segmentation Fault (core dumped)
root at prae> pstack core
core ''core'' of 101364: dtrace -n syscall::open*:entry {
printf("%s %s",execname,copyinstr(arg
fffffd7fff30826a dt_ident_cook () + 32
fffffd7fff31a011 dt_cook_func () + 21
fffffd7fff31d61b dt_node_cook () + 33
fffffd7fff31c681 dt_cook_op3 () + 31
fffffd7fff31d61b dt_node_cook () + 33
fffffd7fff31cda7 dt_cook_member () + 17
fffffd7fff31d61b dt_node_cook () + 33
fffffd7fff31ce8d dt_cook_xlator () + bd
fffffd7fff31d61b dt_node_cook () + 33
fffffd7fff31924d dt_node_xlator () + 1c5
fffffd7fff2eb09b yyparse () + 6a3
fffffd7fff2f7ea4 dt_compile () + 294
fffffd7fff2f83cf dtrace_program_fcompile () + 27
fffffd7fff2f7a9a dt_load_libs_dir () + 11a
fffffd7fff2f7bde dt_load_libs () + 3e
fffffd7fff2f7c83 dt_compile () + 73
fffffd7fff2f839e dtrace_program_strcompile () + 26
0000000000404a80 compile_str () + 40
0000000000406e31 main () + bd1
00000000004031bc ???????? ()
root at prae> mdb core
Loading modules: [ libproc.so.1 libc.so.1 ld.so.1 ]> $?
no process
SIGSEGV: Segmentation Fault
%rax = 0xffdfead000050606 %r8 = 0x00006a2de8000506
%rbx = 0x0000000000000000 %r9 = 0x00000000004c8fd0
%rcx = 0x0000000000000005 %r10 = 0x0000000000000000
%rdx = 0x0000000000000000 %r11 = 0xffffffffffffffff
%rsi = 0x0000000000000005 %r12 = 0x0000000000515f90
%rdi = 0x0000000000000000 %r13 = 0x00000000006a2dc0
%r14 = 0x00000000ffdfead0
%r15 = 0x00000000006a3d10
%cs = 0x0053 %fs = 0x0000 %gs = 0x0000
%ds = 0x0000 %es = 0x0000 %ss = 0x004b
%rip = 0xfffffd7fff30826a libdtrace.so.1`dt_ident_cook+0x32
%rbp = 0xfffffd7fffdfeb10
%rsp = 0xfffffd7fffdfeae0
%rflags = 0x00010202
id=0 vip=0 vif=0 ac=0 vm=0 rf=1 nt=0 iopl=0x0
status=<of,df,IF,tf,sf,zf,af,pf,cf>
%gsbase = 0x0000000000000000
%fsbase = 0xfffffd7ffef60200
%trapno = 0xe
%err = 0x4
--
This message posted from opensolaris.org
Peter Dennis - Solaris Sustaining Engineering
2007-Aug-09 09:51 UTC
[dtrace-discuss] Dtrace - Segmentation Fault
Hi Doug, What compiler did you use to build the image ? Thanks pete Doug Scott wrote:> After building and bfu''in the lastest ON build, any time I run a dtrace script I get a Seg Fault. Is there a dtrace for dtrace :) > > Doug > > root at prae> dtrace -n ''syscall::open*:entry { printf("%s %s",execname,copyinstr(arg0)); }'' > Segmentation Fault (core dumped) > root at prae> pstack core > core ''core'' of 101364: dtrace -n syscall::open*:entry { printf("%s %s",execname,copyinstr(arg > fffffd7fff30826a dt_ident_cook () + 32 > fffffd7fff31a011 dt_cook_func () + 21 > fffffd7fff31d61b dt_node_cook () + 33 > fffffd7fff31c681 dt_cook_op3 () + 31 > fffffd7fff31d61b dt_node_cook () + 33 > fffffd7fff31cda7 dt_cook_member () + 17 > fffffd7fff31d61b dt_node_cook () + 33 > fffffd7fff31ce8d dt_cook_xlator () + bd > fffffd7fff31d61b dt_node_cook () + 33 > fffffd7fff31924d dt_node_xlator () + 1c5 > fffffd7fff2eb09b yyparse () + 6a3 > fffffd7fff2f7ea4 dt_compile () + 294 > fffffd7fff2f83cf dtrace_program_fcompile () + 27 > fffffd7fff2f7a9a dt_load_libs_dir () + 11a > fffffd7fff2f7bde dt_load_libs () + 3e > fffffd7fff2f7c83 dt_compile () + 73 > fffffd7fff2f839e dtrace_program_strcompile () + 26 > 0000000000404a80 compile_str () + 40 > 0000000000406e31 main () + bd1 > 00000000004031bc ???????? () > > root at prae> mdb core > Loading modules: [ libproc.so.1 libc.so.1 ld.so.1 ] >> $? > no process > SIGSEGV: Segmentation Fault > %rax = 0xffdfead000050606 %r8 = 0x00006a2de8000506 > %rbx = 0x0000000000000000 %r9 = 0x00000000004c8fd0 > %rcx = 0x0000000000000005 %r10 = 0x0000000000000000 > %rdx = 0x0000000000000000 %r11 = 0xffffffffffffffff > %rsi = 0x0000000000000005 %r12 = 0x0000000000515f90 > %rdi = 0x0000000000000000 %r13 = 0x00000000006a2dc0 > %r14 = 0x00000000ffdfead0 > %r15 = 0x00000000006a3d10 > > %cs = 0x0053 %fs = 0x0000 %gs = 0x0000 > %ds = 0x0000 %es = 0x0000 %ss = 0x004b > > %rip = 0xfffffd7fff30826a libdtrace.so.1`dt_ident_cook+0x32 > %rbp = 0xfffffd7fffdfeb10 > %rsp = 0xfffffd7fffdfeae0 > > %rflags = 0x00010202 > id=0 vip=0 vif=0 ac=0 vm=0 rf=1 nt=0 iopl=0x0 > status=<of,df,IF,tf,sf,zf,af,pf,cf> > > %gsbase = 0x0000000000000000 > %fsbase = 0xfffffd7ffef60200 > %trapno = 0xe > %err = 0x4 > > > -- > This message posted from opensolaris.org > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org
> Hi Doug, > > What compiler did you use to build the image ? > > Thanks > pete >root at prae> SPRO_ROOT=/opt/SUNWspro root at prae> cc -V cc: Sun C 5.9 SunOS_i386 2007/05/03 usage: cc [ options] files. Use ''cc -flags'' for details -- This message posted from opensolaris.org
I forgot gcc :) It says it is using /usr/sfw/bin/gcc. I do have a later version of gcc and binutils installed as well. I will uninstall them and do another build. Doug nightly.sh version 1.116 2007/07/17 /opt/SUNWspro/bin/dmake dmake: Sun Distributed Make 7.8 SunOS_i386 2007/05/03 number of concurrent jobs = 4 32-bit compiler /opt/onbld/bin/i386/cw -_cc cw version 1.22 primary: /opt/SUNWspro/bin/cc cc: Sun C 5.9 SunOS_i386 2007/05/03 shadow: /usr/sfw/bin/gcc gcc (GCC) 3.4.3 (csl-sol210-3_4-20050802) 64-bit compiler /opt/onbld/bin/i386/cw -_cc cw version 1.22 primary: /opt/SUNWspro/bin/cc cc: Sun C 5.9 SunOS_i386 2007/05/03 shadow: /usr/sfw/bin/gcc gcc (GCC) 3.4.3 (csl-sol210-3_4-20050802) -- This message posted from opensolaris.org
Peter Dennis - Solaris Sustaining Engineering
2007-Aug-09 11:43 UTC
[dtrace-discuss] Dtrace - Segmentation Fault
Doug Scott wrote:>> Hi Doug, >> >> What compiler did you use to build the image ? >> >> Thanks >> pete >> > > root at prae> SPRO_ROOT=/opt/SUNWspro > root at prae> cc -V > cc: Sun C 5.9 SunOS_i386 2007/05/03 > usage: cc [ options] files. Use ''cc -flags'' for detailsAh that is the studio 12 compiler. The current supported build compiler is Studio 11. This problem has been seen in testing the new compiler: 6586975 dtrace cores on onnv built with ss12 fcs it is being investigated. Have found other issues using your bfu ? Thanks pete> > > -- > This message posted from opensolaris.org > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org
Peter Dennis - Solaris Sustaining Engineering writes:> Doug Scott wrote: > > cc: Sun C 5.9 SunOS_i386 2007/05/03 > > usage: cc [ options] files. Use ''cc -flags'' for details > > Ah that is the studio 12 compiler. The current supported build > compiler is Studio 11. > > This problem has been seen in testing the new compiler: > > 6586975 dtrace cores on onnv built with ss12 fcsPeople seem to stumble into this and related SS12 problems quite frequently. Perhaps we ought to update `nightly'' so that it bombs out if SS12 is detected, in the same way that we bomb out if an old broken `dmake'' is seen. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
Peter Dennis - Solaris Sustaining Engineering
2007-Aug-09 13:17 UTC
[dtrace-discuss] Dtrace - Segmentation Fault
James Carlson wrote:> Peter Dennis - Solaris Sustaining Engineering writes: >> Doug Scott wrote: >>> cc: Sun C 5.9 SunOS_i386 2007/05/03 >>> usage: cc [ options] files. Use ''cc -flags'' for details >> Ah that is the studio 12 compiler. The current supported build >> compiler is Studio 11. >> >> This problem has been seen in testing the new compiler: >> >> 6586975 dtrace cores on onnv built with ss12 fcs > > People seem to stumble into this and related SS12 problems quite > frequently.Oh. Do you know where such things are reported ?> Perhaps we ought to update `nightly'' so that it bombs out > if SS12 is detected, in the same way that we bomb out if an old broken > `dmake'' is seen.Ummm...in order to build with SS12 you need to set __SSNEXT in the environment and so this is a matter of choice (unless Doug corrects me here). Thanks pete>
Peter Dennis - Solaris Sustaining Engineering writes:> James Carlson wrote: > > Peter Dennis - Solaris Sustaining Engineering writes: > >> 6586975 dtrace cores on onnv built with ss12 fcs > > > > People seem to stumble into this and related SS12 problems quite > > frequently. > > Oh. Do you know where such things are reported ?opensolaris-discuss and opensolaris-code are two places.> > Perhaps we ought to update `nightly'' so that it bombs out > > if SS12 is detected, in the same way that we bomb out if an old broken > > `dmake'' is seen. > > Ummm...in order to build with SS12 you need to set __SSNEXT in > the environment and so this is a matter of choice (unless Doug > corrects me here).If that flag _isn''t_ set, shouldn''t nightly stop you from wandering into this area? -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
Peter Dennis - Solaris Sustaining Engineering
2007-Aug-09 13:38 UTC
[dtrace-discuss] Dtrace - Segmentation Fault
James Carlson wrote:> Peter Dennis - Solaris Sustaining Engineering writes: >> James Carlson wrote: >>> Peter Dennis - Solaris Sustaining Engineering writes: >>>> 6586975 dtrace cores on onnv built with ss12 fcs >>> People seem to stumble into this and related SS12 problems quite >>> frequently. >> Oh. Do you know where such things are reported ? > > opensolaris-discuss and opensolaris-code are two places. >ta.>>> Perhaps we ought to update `nightly'' so that it bombs out >>> if SS12 is detected, in the same way that we bomb out if an old broken >>> `dmake'' is seen. >> Ummm...in order to build with SS12 you need to set __SSNEXT in >> the environment and so this is a matter of choice (unless Doug >> corrects me here). > > If that flag _isn''t_ set, shouldn''t nightly stop you from wandering > into this area?Yes. That is correct (and what I meant).>