|
From: Fred S. <fr...@co...> - 2005-04-05 21:02:57
|
I'm getting this: =0D =3D=3D8217=3D=3D Syscall param write(buf) points to uninitialised byte(s) =3D=3D8217=3D=3D at 0x1C473054: write (in /lib/i686/libc-2.2.4.so) =3D=3D8217=3D=3D by 0x804BCC9: HS_start_inthread (HS_runif.c:84) =3D=3D8217=3D=3D by 0x804BF17: HS_start_oneif (HS_runif.c:202) =3D=3D8217=3D=3D by 0x804C046: HS_start_interfaces (HS_runif.c:238) =3D=3D8217=3D=3D by 0x804B706: main (HS_hl7main.c:389) =3D=3D8217=3D=3D Address 0x52BFE5AC is on thread 1's stack =0D But I don't get it. There are no write() calls anywhere in that call trace. The call at line 84 of HS_runif is a call to pthread_create(). I can't see anything un-initialized in the parameter list, either. Any way to get more detail out of valgrind in cases like this? I'm using RHEL WS 2.1. =0D Fred This email and any files transmitted with it are confidential and intended= solely for the use of the individual or entity to which they are= addressed. If you have received this email in error, please notify the= system manager. Please note that any views or opinions presented in this= email are solely those of the author and do not necessarily represent= those of the company. Finally, the recipient should check this email and= any attachments for the presence of viruses. The company accepts no= liability for any damage caused by any virus transmitted by this email. |
|
From: Dennis L. <pla...@in...> - 2005-04-05 21:12:13
|
FAQ 4.4 At 23:08 05.04.2005, Fred Smith wrote: >I'm getting this: > >==8217== Syscall param write(buf) points to uninitialised byte(s) >==8217== at 0x1C473054: write (in /lib/i686/libc-2.2.4.so) >==8217== by 0x804BCC9: HS_start_inthread (HS_runif.c:84) >==8217== by 0x804BF17: HS_start_oneif (HS_runif.c:202) >==8217== by 0x804C046: HS_start_interfaces (HS_runif.c:238) >==8217== by 0x804B706: main (HS_hl7main.c:389) >==8217== Address 0x52BFE5AC is on thread 1's stack > >But I don't get it. There are no write() calls anywhere in that call >trace. The call at line 84 of HS_runif is a call to pthread_create(). I >can't see anything un-initialized in the parameter list, either. Any way >to get more detail out of valgrind in cases like this? I'm using RHEL WS 2.1. > >Fred >This email and any files transmitted with it are confidential and intended >solely for the use of the individual or entity to which they are >addressed. If you have received this email in error, please notify the >system manager. Please note that any views or opinions presented in this >email are solely those of the author and do not necessarily represent >those of the company. Finally, the recipient should check this email and >any attachments for the presence of viruses. The company accepts no >liability for any damage caused by any virus transmitted by this email. Carpe quod tibi datum est |
|
From: Paul S. <ps...@no...> - 2005-04-05 21:19:35
|
%% Dennis Lubert <pla...@in...> writes: dl> FAQ 4.4 ITYM 5.4 ... ? -- ------------------------------------------------------------------------------- Paul D. Smith <ps...@no...> HASMAT: HA Software Mthds & Tools "Please remain calm...I may be mad, but I am a professional." --Mad Scientist ------------------------------------------------------------------------------- These are my opinions---Nortel Networks takes no responsibility for them. |
|
From: Dennis L. <pla...@in...> - 2005-04-05 21:34:53
|
At 23:20 05.04.2005, you wrote: >On Tue, 5 Apr 2005, Dennis Lubert wrote: > >>FAQ 4.4 > >Huh? 4.4 doesn't address this issue. Well in my version (rather recent CVS) : 4.4 The stack traces given by Memcheck (or another tool) aren't helpful. How can I improve them? If they're not long enough, use --num-callers to make them longer. "There are no write() calls anywhere in that call trace." " Any way to get more detail out of valgrind in cases like this?" My idea : longer stack trace, lookup matched FAQ 4.4 here... greets Dennis Carpe quod tibi datum est |
|
From: Tom H. <to...@co...> - 2005-04-05 22:08:08
|
In message <6.1.2.0.0.20050405233143.04ac9ec0@192.168.5.6>
Dennis Lubert <pla...@in...> wrote:
> At 23:20 05.04.2005, you wrote:
> >On Tue, 5 Apr 2005, Dennis Lubert wrote:
> >
> >>FAQ 4.4
> >
> >Huh? 4.4 doesn't address this issue.
>
>
> Well in my version (rather recent CVS) :
>
> 4.4 The stack traces given by Memcheck (or another tool) aren't helpful.
> How can I improve them?
>
> If they're not long enough, use --num-callers to make them longer.
>
> "There are no write() calls anywhere in that call trace."
> " Any way to get more detail out of valgrind in cases like this?"
>
> My idea : longer stack trace, lookup matched FAQ 4.4 here...
He could see where write was being called from, so a longer stack
trace wouldn't have been of any help at all. His problem was that
the write was being tail called from pthread_create or something
so that the intermediate rouitne vanished from the stack leading
to confusion.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Nicholas N. <nj...@cs...> - 2005-04-05 21:20:42
|
On Tue, 5 Apr 2005, Dennis Lubert wrote: > FAQ 4.4 Huh? 4.4 doesn't address this issue. > At 23:08 05.04.2005, Fred Smith wrote: >> >> ==8217== Syscall param write(buf) points to uninitialised byte(s) >> ==8217== at 0x1C473054: write (in /lib/i686/libc-2.2.4.so) >> ==8217== by 0x804BCC9: HS_start_inthread (HS_runif.c:84) >> ==8217== by 0x804BF17: HS_start_oneif (HS_runif.c:202) >> ==8217== by 0x804C046: HS_start_interfaces (HS_runif.c:238) >> ==8217== by 0x804B706: main (HS_hl7main.c:389) >> ==8217== Address 0x52BFE5AC is on thread 1's stack >> >> But I don't get it. There are no write() calls anywhere in that call trace. Huh? What about the 2nd line? >> The call at line 84 of HS_runif is a call to pthread_create(). I can't see >> anything un-initialized in the parameter list, either. Any way to get more >> detail out of valgrind in cases like this? I'm using RHEL WS 2.1. This is caused by the pthreads library, not your code. You can safely ignore it; just create a suppression for the error. N |