This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Probably bugreport


Hello,

I think that I found one bug in glibc-2.5-34 and older.

I have attached source-code example and a cut of my log on x86_64-machine. As we can see in the log and source code, there's an "Invalid read" in memcpy() from variable, that was been allocated by opendir(). And I don't see any error in my source code example to make the "Invalid read". :)

To repeat the error, I should to follow this instructions on CentOS-5.*, x86_64:
1.) tar -xzf probablybug.tar.gz
2.) cd probablybug
3.) make
4.) /Invalid<enter>


Can you fix my mind and explain where was I wrong? :)

Regards,

--
Nick: Xaionaro
Name: Dmitry J Okunev
Phone: +7 906 734 41 55
Email: <mailto:d.okunev@rosnet.ru>
Company: Rosnet

Attachment: probablybug.tar.gz
Description: GNU Zip compressed data

46.) 0x7ff000850 <200807091725001000000054_D_3_FTPDRV_IPPROCWEB_F_0_0_0_0_0.msg>0x402afcb 88
47.) 0x7ff000850 <200807091725001000000035_D_3_FTPDRV_IPPROCWEB_F_0_0_0_0_0.msg>0x402b023 88
==2152== Invalid read of size 1
==2152==    at 0x40065A: main (t.c:24)
==2152==  Address 0x402B068 is 0 bytes after a block of size 4,152 alloc'd
==2152==    at 0x4C20809: malloc (vg_replace_malloc.c:149)
==2152==    by 0x4EB9638: __alloc_dir (in /lib64/libc-2.5.so)
==2152==    by 0x4EB9707: opendir (in /lib64/libc-2.5.so)
==2152==    by 0x4005D3: main (t.c:19)
48.) 0x7ff000850 <200807091725001000000065_D_3_FTPDRV_IPPROCWEB_F_0_0_0_0_0.msg>0x402a07b 88
49.) 0x7ff000850 <200807091725001000000023_D_3_FTPDRV_IPPROCWEB_F_0_0_0_0_0.msg>0x402a0d3 88

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]