On Wed, Oct 20, 2010 at 1:25 PM, Dale <rdalek1...@gmail.com> wrote:
> I appear to have another issue to deal with right now. This is weird. When
> I type in any nvclock command, I get something like this:
>
> r...@smoker / # nvclock -i
> *** buffer overflow detected ***: nvclock terminated
Seems like maybe that is glibc stopping you from running a program
with a (potential) buffer overflow. You can set an environment
variable to make it stop doing that and let you run the program
anyway, assuming you don't want to edit nvclock's source code to fix
the problem. :)
Try:
MALLOC_CHECK_=0 nvclock -i
("man malloc" for more info)
