Hi folks,

While checking some things earlier today I ran into a little issue. It
seems glibc, nvclock or something has a issue and I'm not sure which one
it would be. System info:


root@smoker / # emerge --info
Portage 2.2_rc98 (default/linux/x86/10.0/desktop/kde, gcc-4.4.3,
glibc-2.11.2-r0, 2.6.35-gentoo-r4 i686)

================================================== ===============
System uname:
Linux-2.6.35-gentoo-r4-i686-AMD_Athlon-tm-_XP_2500+-with-gentoo-1.12.13

Timestamp of tree: Wed, 20 Oct 2010 22:15:02 +0000
app-shells/bash: 4.1_p7
dev-java/java-config: 2.1.11
dev-lang/python: 2.6.5-r3, 3.1.2-r4
dev-util/cmake: 2.8.1-r2
sys-apps/baselayout: 1.12.13
sys-apps/sandbox: 2.3-r1
sys-devel/autoconf: 2.13, 2.65-r1
sys-devel/automake: 1.8.5-r4, 1.9.6-r3, 1.10.3, 1.11.1
sys-devel/binutils: 2.20.1-r1
sys-devel/gcc: 4.4.3-r2
sys-devel/gcc-config: 1.4.1
sys-devel/libtool: 2.2.10
sys-devel/make: 3.81-r2
virtual/os-headers: 2.6.35 (sys-kernel/linux-headers)

I shortened that a bit but I think it has all that is needed. If not,
let me know. This is the error I get:


root@smoker / # nvclock -i
*** buffer overflow detected ***: nvclock terminated
======= Backtrace: =========
/lib/libc.so.6(__fortify_fail+0x50)[0xb7589850]
/lib/libc.so.6(+0xe18aa)[0xb75878aa]
/lib/libc.so.6(+0xe0f78)[0xb7586f78]
/lib/libc.so.6(__overflow+0x4a)[0xb751070a]
/lib/libc.so.6(_IO_vfprintf+0x50b9)[0xb74e7b39]
/lib/libc.so.6(__vsprintf_chk+0xa7)[0xb7587027]
/lib/libc.so.6(__sprintf_chk+0x2d)[0xb7586f6d]
nvclock[0x8057317]
[0x30322e34]
======= Memory map: ========
08048000-08060000 r-xp 00000000 08:16 311032 /usr/bin/nvclock
08060000-08061000 r--p 00017000 08:16 311032 /usr/bin/nvclock
08061000-08062000 rw-p 00018000 08:16 311032 /usr/bin/nvclock
082d0000-082f1000 rw-p 00000000 00:00 0 [heap]
b72f9000-b7315000 r-xp 00000000 08:16 2070143
/usr/lib/gcc/i686-pc-linux-gnu/4.4.3/libgcc_s.so.1
b7315000-b7316000 r--p 0001b000 08:16 2070143
/usr/lib/gcc/i686-pc-linux-gnu/4.4.3/libgcc_s.so.1
b7316000-b7317000 rw-p 0001c000 08:16 2070143
/usr/lib/gcc/i686-pc-linux-gnu/4.4.3/libgcc_s.so.1

b733a000-b734a000 rw-s dc300000 00:0d 8375 /dev/nvidia0
b734a000-b744a000 rw-s dc700000 00:0d 8375 /dev/nvidia0
b744a000-b747a000 rw-s dc000000 00:0d 8375 /dev/nvidia0
b747a000-b747b000 rw-p 00000000 00:00 0
b747b000-b747f000 r-xp 00000000 08:16 242258 /usr/lib/libXdmcp.so.6.0.0
b747f000-b7480000 r--p 00003000 08:16 242258 /usr/lib/libXdmcp.so.6.0.0
b7480000-b7481000 rw-p 00004000 08:16 242258 /usr/lib/libXdmcp.so.6.0.0
b7481000-b7483000 r-xp 00000000 08:16 179499 /usr/lib/libXau.so.6.0.0
b7483000-b7484000 r--p 00001000 08:16 179499 /usr/lib/libXau.so.6.0.0
b7484000-b7485000 rw-p 00002000 08:16 179499 /usr/lib/libXau.so.6.0.0
b7485000-b7486000 rw-p 00000000 00:00 0
b7486000-b7488000 r-xp 00000000 08:16 3019384 /lib/libdl-2.11.2.so
b7488000-b7489000 r--p 00001000 08:16 3019384 /lib/libdl-2.11.2.so
b7489000-b748a000 rw-p 00002000 08:16 3019384 /lib/libdl-2.11.2.so
b748a000-b74a4000 r-xp 00000000 08:16 2178229 /usr/lib/libxcb.so.1.1.0
b74a4000-b74a5000 r--p 00019000 08:16 2178229 /usr/lib/libxcb.so.1.1.0
b74a5000-b74a6000 rw-p 0001a000 08:16 2178229 /usr/lib/libxcb.so.1.1.0
b74a6000-b75e6000 r-xp 00000000 08:16 3018521 /lib/libc-2.11.2.so
b75e6000-b75e8000 r--p 0013f000 08:16 3018521 /lib/libc-2.11.2.so
b75e8000-b75e9000 rw-p 00141000 08:16 3018521 /lib/libc-2.11.2.so
b75e9000-b75ec000 rw-p 00000000 00:00 0
b75ec000-b75fa000 r-xp 00000000 08:16 623393 /usr/lib/libXext.so.6.4.0
b75fa000-b75fb000 r--p 0000d000 08:16 623393 /usr/lib/libXext.so.6.4.0
b75fb000-b75fc000 rw-p 0000e000 08:16 623393 /usr/lib/libXext.so.6.4.0
b75fc000-b7718000 r-xp 00000000 08:16 2143515 /usr/lib/libX11.so.6.3.0
b7718000-b7719000 r--p 0011b000 08:16 2143515 /usr/lib/libX11.so.6.3.0
b7719000-b771c000 rw-p 0011c000 08:16 2143515 /usr/lib/libX11.so.6.3.0
b7729000-b772b000 rw-s dc680000 00:0d 8375 /dev/nvidia0
b772b000-b773b000 rw-s dc610000 00:0d 8375 /dev/nvidia0
b773b000-b773d000 rw-s dc601000 00:0d 8375 /dev/nvidia0
b773d000-b773e000 rw-s dc100000 00:0d 8375 /dev/nvidia0
b773e000-b773f000 rw-s dc101000 00:0d 8375 /dev/nvidia0
b773f000-b7740000 rw-p 00000000 00:00 0
b7740000-b7741000 r-xp 00000000 00:00 0 [vdso]
b7741000-b775d000 r-xp 00000000 08:16 3019734 /lib/ld-2.11.2.so
b775d000-b775e000 r--p 0001b000 08:16 3019734 /lib/ld-2.11.2.so
b775e000-b775f000 rw-p 0001c000 08:16 3019734 /lib/ld-2.11.2.so
bf8be000-bf8df000 rw-p 00000000 00:00 0 [stack]
Aborted
root@smoker / #


So, is this nvclock? Is it gcc? Is it glibc? Is it something else? I
haven't seen this with any other program so I'm thinking nvidia but I'm
using the only version that provides nvclock in the tree. Sort of stuck
here.


Thoughts? Ideas?

Dale

:-) :-)

On 10/20/2010 05:32 PM, Dale wrote:

Hi folks,

While checking some things earlier today I ran into a little issue. It seems glibc, nvclock or something has a issue and I'm not sure which one it would be. System info:



So, is this nvclock? Is it gcc? Is it glibc? Is it something else? I haven't seen this with any other program so I'm thinking nvidia but I'm using the only version that provides nvclock in the tree. Sort of stuck here.


Does nvclock require X to be running? If not, try running it from a console.
If nvclock is an X application you could try using a different video driver
like nv or vesa to rule out nvidia.

walt wrote:

On 10/20/2010 05:32 PM, Dale wrote:

Hi folks,

While checking some things earlier today I ran into a little issue.
It seems glibc, nvclock or something has a issue and I'm not sure
which one it would be. System info:


So, is this nvclock? Is it gcc? Is it glibc? Is it something else? I
haven't seen this with any other program so I'm thinking nvidia but
I'm using the only version that provides nvclock in the tree. Sort of
stuck here.


Does nvclock require X to be running? If not, try running it from a
console.
If nvclock is an X application you could try using a different video
driver

like nv or vesa to rule out nvidia.




I tried this in a Console, a Konsole as both root and a user. I get the
same error.


I also noticed there was a keyworded version of glibc that looked like
the version I was running with a bug fix. I upgraded to it and still
get the same error.


I'm not sure what else to try since I don't know what is broke.

Still open to ideas tho.

Dale

:-) :-)