|
From: Sudarshan S. <sud...@gm...> - 2008-05-22 06:12:47
|
Hi, I am getting the following error when i try to run valgrind-3.2.3 on ppc machine. Can anyone please let me know if there is any problem with the way i built valgrind or any other issue. (i used the following to build valgrind sources /configure --host=powerpc-linux --disable-tls make make install) error log: bash-2.05# ./valgrind /bin/date ==3468== Memcheck, a memory error detector. ==3468== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al. ==3468== Using LibVEX rev 1732, a library for dynamic binary translation. ==3468== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP. ==3468== Using valgrind-3.2.3, a dynamic binary instrumentation framework. ==3468== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al. ==3468== For more details, rerun with: -v ==3468== ==3468== ==3468== Process terminating with default action of signal 11 (SIGSEGV) ==3468== Bad permissions for mapped region at address 0x4024BF4 ==3468== at 0x4024BF4: ??? ==3468== by 0x40100E4: (within /lib/ld-2.2.5.so) ==3468== ==3468== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==3468== malloc/free: in use at exit: 0 bytes in 0 blocks. ==3468== malloc/free: 0 allocs, 0 frees, 0 bytes allocated. ==3468== For counts of detected errors, rerun with: -v ==3468== All heap blocks were freed -- no leaks are possible. Segmentation fault bash-2.05# Regards , Pavan |
|
From: Bart V. A. <bar...@gm...> - 2008-05-22 06:24:29
|
On Thu, May 22, 2008 at 8:12 AM, Sudarshan Soma <sud...@gm...> wrote: > bash-2.05# ./valgrind /bin/date > ... > ==3468== Process terminating with default action of signal 11 (SIGSEGV) Maybe it's a good idea to file a bug report. Instructions can be found here: http://www.valgrind.org/support/bug_reports.html Bart. |
|
From: Sudarshan S. <sud...@gm...> - 2008-05-22 06:49:29
|
Yes its done now. http://bugs.kde.org/show_bug.cgi?id=162456 Thanks Pavan On 5/22/08, Bart Van Assche <bar...@gm...> wrote: > On Thu, May 22, 2008 at 8:12 AM, Sudarshan Soma <sud...@gm...> wrote: > > bash-2.05# ./valgrind /bin/date > > ... > > > ==3468== Process terminating with default action of signal 11 (SIGSEGV) > > > Maybe it's a good idea to file a bug report. Instructions can be found here: > http://www.valgrind.org/support/bug_reports.html > > > Bart. > |
|
From: Bart V. A. <bar...@gm...> - 2008-05-22 15:09:43
|
On Thu, May 22, 2008 at 8:49 AM, Sudarshan Soma <sud...@gm...> wrote: > Yes its done now. > > http://bugs.kde.org/show_bug.cgi?id=162456 > > Thanks > Pavan Can you please follow the steps outlined in README_DEVELOPERS and include the gdb-call stack in the bug report ? Thanks, Bart. |
|
From: Sudarshan S. <sud...@gm...> - 2008-05-23 05:15:56
|
Hi Bart, gdb is not currently available, i will try to grt that and
let you know the trace. I have made the following information for now:
Let me know if this helps.
Regards,
Sudarshan
logs:
bash-2.05# ./valgrind --vex-guest-chase-thresh=0
--trace-flags=10000000 --trace-notbelow=999999 /bin/date
==4709== Memcheck, a memory error detector.
==4709== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==4709== Using LibVEX rev 1732, a library for dynamic binary translation.
==4709== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==4709== Using valgrind-3.2.3, a dynamic binary instrumentation framework.
==4709== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==4709== For more details, rerun with: -v
==4709==
==== BB 0 (0x40100D4) BBs exec'd 0 ====
==== BB 1 (0x4001D60) BBs exec'd 1 ====
==== BB 2 (0x4001DA4) BBs exec'd 2 ====
==== BB 3 (0x4024BF4) BBs exec'd 3 ====
==4709==
==4709== Process terminating with default action of signal 11 (SIGSEGV)
==4709== Bad permissions for mapped region at address 0x4024BF4
==4709== at 0x4024BF4: ???
==4709== by 0x40100E4: (within /lib/ld-2.2.5.so)
==4709==
==4709== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==4709== malloc/free: in use at exit: 0 bytes in 0 blocks.
==4709== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
==4709== For counts of detected errors, rerun with: -v
==4709== All heap blocks were freed -- no leaks are possible.
Segmentation fault
bash-2.05#
bash-2.05# ./valgrind --vex-guest-chase-thresh=0
--trace-flags=10000000 --trace-notbelow=0x4024BF4 /bin/date
==4706== Memcheck, a memory error detector.
==4706== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==4706== Using LibVEX rev 1732, a library for dynamic binary translation.
==4706== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==4706== Using valgrind-3.2.3, a dynamic binary instrumentation framework.
==4706== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==4706== For more details, rerun with: -v
==4706==
==== BB 0 (0x40100D4) BBs exec'd 0 ====
------------------------ Front end ------------------------
0x40100D4: mr r3,r1
------ IMark(0x40100D4, 4) ------
t0 = GET:I32(4)
t2 = GET:I32(4)
t1 = t0
PUT(12) = t1
0x40100D8: li r4,0
------ IMark(0x40100D8, 4) ------
PUT(896) = 0x40100D8:I32
t3 = GET:I32(0)
t4 = GET:I32(0)
t5 = 0x0:I32
PUT(16) = t5
0x40100DC: addi r1,r1,-16
------ IMark(0x40100DC, 4) ------
PUT(896) = 0x40100DC:I32
t6 = GET:I32(4)
t7 = GET:I32(124)
t8 = Add32(t6,0xFFFFFFF0:I32)
PUT(4) = t8
0x40100E0: stw r4,0(r1)
------ IMark(0x40100E0, 4) ------
PUT(896) = 0x40100E0:I32
t10 = GET:I32(0)
t9 = GET:I32(16)
t11 = Add32(GET:I32(4),0x0:I32)
STbe(t11) = t9
0x40100E4: bl 0x4001D60
------ IMark(0x40100E4, 4) ------
PUT(896) = 0x40100E4:I32
PUT(900) = 0x40100E8:I32
goto {Call} 0x4001D60:I32
. 0 40100D4 20
. 7C 23 0B 78 38 80 00 00 38 21 FF F0 90 81 00 00 4B FF 1C 7D
==== BB 1 (0x4001D60) BBs exec'd 1 ====
------------------------ Front end ------------------------
0x4001D60: stwu r1,-544(r1)
------ IMark(0x4001D60, 4) ------
t1 = GET:I32(124)
t0 = GET:I32(4)
t2 = Add32(GET:I32(4),0xFFFFFDE0:I32)
PUT(4) = t2
STbe(t2) = t0
0x4001D64: mflr r0
------ IMark(0x4001D64, 4) ------
PUT(896) = 0x4001D64:I32
t3 = GET:I32(0)
PUT(0) = GET:I32(900)
0x4001D68: stw r20,496(r1)
------ IMark(0x4001D68, 4) ------
PUT(896) = 0x4001D68:I32
t5 = GET:I32(0)
t4 = GET:I32(80)
t6 = Add32(GET:I32(4),0x1F0:I32)
STbe(t6) = t4
0x4001D6C: stw r21,500(r1)
------ IMark(0x4001D6C, 4) ------
PUT(896) = 0x4001D6C:I32
t8 = GET:I32(0)
t7 = GET:I32(84)
t9 = Add32(GET:I32(4),0x1F4:I32)
STbe(t9) = t7
0x4001D70: stw r22,504(r1)
------ IMark(0x4001D70, 4) ------
PUT(896) = 0x4001D70:I32
t11 = GET:I32(0)
t10 = GET:I32(88)
t12 = Add32(GET:I32(4),0x1F8:I32)
STbe(t12) = t10
0x4001D74: stw r23,508(r1)
------ IMark(0x4001D74, 4) ------
PUT(896) = 0x4001D74:I32
t14 = GET:I32(0)
t13 = GET:I32(92)
t15 = Add32(GET:I32(4),0x1FC:I32)
STbe(t15) = t13
0x4001D78: stw r24,512(r1)
------ IMark(0x4001D78, 4) ------
PUT(896) = 0x4001D78:I32
t17 = GET:I32(0)
t16 = GET:I32(96)
t18 = Add32(GET:I32(4),0x200:I32)
STbe(t18) = t16
0x4001D7C: stw r25,516(r1)
------ IMark(0x4001D7C, 4) ------
PUT(896) = 0x4001D7C:I32
t20 = GET:I32(0)
t19 = GET:I32(100)
t21 = Add32(GET:I32(4),0x204:I32)
STbe(t21) = t19
0x4001D80: stw r26,520(r1)
------ IMark(0x4001D80, 4) ------
PUT(896) = 0x4001D80:I32
t23 = GET:I32(0)
t22 = GET:I32(104)
t24 = Add32(GET:I32(4),0x208:I32)
STbe(t24) = t22
0x4001D84: stw r27,524(r1)
------ IMark(0x4001D84, 4) ------
PUT(896) = 0x4001D84:I32
t26 = GET:I32(0)
t25 = GET:I32(108)
t27 = Add32(GET:I32(4),0x20C:I32)
STbe(t27) = t25
0x4001D88: stw r28,528(r1)
------ IMark(0x4001D88, 4) ------
PUT(896) = 0x4001D88:I32
t29 = GET:I32(0)
t28 = GET:I32(112)
t30 = Add32(GET:I32(4),0x210:I32)
STbe(t30) = t28
0x4001D8C: stw r29,532(r1)
------ IMark(0x4001D8C, 4) ------
PUT(896) = 0x4001D8C:I32
t32 = GET:I32(0)
t31 = GET:I32(116)
t33 = Add32(GET:I32(4),0x214:I32)
STbe(t33) = t31
0x4001D90: stw r30,536(r1)
------ IMark(0x4001D90, 4) ------
PUT(896) = 0x4001D90:I32
t35 = GET:I32(0)
t34 = GET:I32(120)
t36 = Add32(GET:I32(4),0x218:I32)
STbe(t36) = t34
0x4001D94: stw r31,540(r1)
------ IMark(0x4001D94, 4) ------
PUT(896) = 0x4001D94:I32
t38 = GET:I32(0)
t37 = GET:I32(124)
t39 = Add32(GET:I32(4),0x21C:I32)
STbe(t39) = t37
0x4001D98: stw r0,548(r1)
------ IMark(0x4001D98, 4) ------
PUT(896) = 0x4001D98:I32
t41 = GET:I32(0)
t40 = GET:I32(0)
t42 = Add32(GET:I32(4),0x224:I32)
STbe(t42) = t40
0x4001D9C: bl 0x4001DA4
------ IMark(0x4001D9C, 4) ------
PUT(896) = 0x4001D9C:I32
PUT(900) = 0x4001DA0:I32
goto {Call} 0x4001DA4:I32
. 0 4001D60 64
. 94 21 FD E0 7C 08 02 A6 92 81 01 F0 92 A1 01 F4 92 C1 01 F8 92 E1 01
FC 93 01 02 00 93 21 02 04 93 41 02 08 93 61 02 0C 93 81 02 10 93 A1
02 14 93 C1 02 18 93 E1 02 1C 90 01 02 24 48 00 00 09
==== BB 2 (0x4001DA4) BBs exec'd 2 ====
------------------------ Front end ------------------------
0x4001DA4: li r7,53
------ IMark(0x4001DA4, 4) ------
t0 = GET:I32(0)
t1 = GET:I32(0)
t2 = 0x35:I32
PUT(28) = t2
0x4001DA8: mflr r11
------ IMark(0x4001DA8, 4) ------
PUT(896) = 0x4001DA8:I32
t3 = GET:I32(44)
PUT(44) = GET:I32(900)
0x4001DAC: mtctr r7
------ IMark(0x4001DAC, 4) ------
PUT(896) = 0x4001DAC:I32
t4 = GET:I32(28)
PUT(904) = t4
0x4001DB0: bl 0x4024BF4
------ IMark(0x4001DB0, 4) ------
PUT(896) = 0x4001DB0:I32
PUT(900) = 0x4001DB4:I32
goto {Call} 0x4024BF4:I32
. 0 4001DA4 16
. 38 E0 00 35 7D 68 02 A6 7C E9 03 A6 48 02 2E 45
==== BB 3 (0x4024BF4) BBs exec'd 3 ====
==4706==
==4706== Process terminating with default action of signal 11 (SIGSEGV)
==4706== Bad permissions for mapped region at address 0x4024BF4
==4706== at 0x4024BF4: ???
==4706== by 0x40100E4: (within /lib/ld-2.2.5.so)
==4706==
==4706== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==4706== malloc/free: in use at exit: 0 bytes in 0 blocks.
==4706== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
==4706== For counts of detected errors, rerun with: -v
==4706== All heap blocks were freed -- no leaks are possible.
Segmentation fault
On 5/22/08, Bart Van Assche <bar...@gm...> wrote:
> On Thu, May 22, 2008 at 8:49 AM, Sudarshan Soma <sud...@gm...> wrote:
> > Yes its done now.
> >
> > http://bugs.kde.org/show_bug.cgi?id=162456
> >
> > Thanks
> > Pavan
>
>
> Can you please follow the steps outlined in README_DEVELOPERS and
> include the gdb-call stack in the bug report ?
>
> Thanks,
>
>
> Bart.
>
|
|
From: Bart V. A. <bar...@gm...> - 2008-05-23 06:05:42
|
On Fri, May 23, 2008 at 7:15 AM, Sudarshan Soma <sud...@gm...> wrote: > Hi Bart, gdb is not currently available, i will try to grt that and > let you know the trace. I have made the following information for now: > > Let me know if this helps. > > Regards, > Sudarshan > > > logs: > bash-2.05# ./valgrind --vex-guest-chase-thresh=0 > --trace-flags=10000000 --trace-notbelow=999999 /bin/date This log only helps if the crash is triggered by processing a specific instruction, which is unlikely. The gdb call stack is really needed in order to know the cause of the segmentation fault. See e.g. http://bugs.kde.org/show_bug.cgi?id=162482 Bart. |