[Bug 72117] Re: Stack Smashing Prevents Use
the fix is still in lucid, don't reopen closed bugs but open a new ticket rather for your issue ** Changed in: nvclock (Ubuntu) Status: New = Fix Released -- Stack Smashing Prevents Use https://bugs.launchpad.net/bugs/72117 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
In Lucid the problem has returnd, so its new ** Changed in: nvclock (Ubuntu) Status: Fix Released = New -- Stack Smashing Prevents Use https://bugs.launchpad.net/bugs/72117 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
Hi there, try modifying backend/bios.c in function verify_bios like this... /* All bioses start with this '0x55 0xAA' signature */ if((rom[0] != (char)0x55) || ((rom[1] 0xff) != (char)0xAA)) return 0; Don't know why rom[1] is 0xff55 when my sizeof(char) is 1 :( but this solves problem with stack smashing in my case (Ti4200) Good luck -- Stack Smashing Prevents Use https://bugs.launchpad.net/bugs/72117 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
Houls I fill in new bug report? -- Stack Smashing Prevents Use https://bugs.launchpad.net/bugs/72117 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
As miky91 noted, it happens in Jaunty. E. g. y...@spacecraft:~$ nvclock -T *** stack smashing detected ***: nvclock terminated === Backtrace: = /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb7eb5da8] /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0xb7eb5d60] nvclock[0x8058e39] nvclock[0x805adf7] nvclock[0x805ab65] nvclock[0x804e560] nvclock[0x804dd20] nvclock[0x8057e62] nvclock[0x804a39e] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7dce775] nvclock[0x8049201] === Memory map: 08048000-08063000 r-xp 08:03 847241 /usr/bin/nvclock 08063000-08064000 r--p 0001a000 08:03 847241 /usr/bin/nvclock 08064000-08065000 rw-p 0001b000 08:03 847241 /usr/bin/nvclock 09c5b000-09c7c000 rw-p 09c5b000 00:00 0 [heap] b7c26000-b7c33000 r-xp 08:03 244390 /lib/libgcc_s.so.1 b7c33000-b7c34000 r--p c000 08:03 244390 /lib/libgcc_s.so.1 b7c34000-b7c35000 rw-p d000 08:03 244390 /lib/libgcc_s.so.1 b7c4f000-b7c5f000 rw-s fc30 00:0f 7044 /dev/nvidia0 b7c5f000-b7d5f000 rw-s fc70 00:0f 7044 /dev/nvidia0 b7d5f000-b7d8f000 rw-s fc00 00:0f 7044 /dev/nvidia0 b7d8f000-b7d91000 rw-p b7d8f000 00:00 0 b7d91000-b7d95000 r-xp 08:03 848058 /usr/lib/libXdmcp.so.6.0.0 b7d95000-b7d96000 rw-p 3000 08:03 848058 /usr/lib/libXdmcp.so.6.0.0 b7d96000-b7d98000 r-xp 08:03 845795 /usr/lib/libXau.so.6.0.0 b7d98000-b7d99000 r--p 1000 08:03 845795 /usr/lib/libXau.so.6.0.0 b7d99000-b7d9a000 rw-p 2000 08:03 845795 /usr/lib/libXau.so.6.0.0 b7d9a000-b7d9c000 r-xp 08:03 278240 /lib/tls/i686/cmov/libdl-2.9.so b7d9c000-b7d9d000 r--p 1000 08:03 278240 /lib/tls/i686/cmov/libdl-2.9.so b7d9d000-b7d9e000 rw-p 2000 08:03 278240 /lib/tls/i686/cmov/libdl-2.9.so b7d9e000-b7db6000 r-xp 08:03 847283 /usr/lib/libxcb.so.1.1.0 b7db6000-b7db7000 r--p 00017000 08:03 847283 /usr/lib/libxcb.so.1.1.0 b7db7000-b7db8000 rw-p 00018000 08:03 847283 /usr/lib/libxcb.so.1.1.0 b7db8000-b7f14000 r-xp 08:03 278237 /lib/tls/i686/cmov/libc-2.9.so b7f14000-b7f15000 ---p 0015c000 08:03 278237 /lib/tls/i686/cmov/libc-2.9.so b7f15000-b7f17000 r--p 0015c000 08:03 278237 /lib/tls/i686/cmov/libc-2.9.so b7f17000-b7f18000 rw-p 0015e000 08:03 278237 /lib/tls/i686/cmov/libc-2.9.so b7f18000-b7f1c000 rw-p b7f18000 00:00 0 b7f1c000-b7f2a000 r-xp 08:03 845424 /usr/lib/libXext.so.6.4.0 b7f2a000-b7f2b000 r--p d000 08:03 845424 /usr/lib/libXext.so.6.4.0 b7f2b000-b7f2c000 rw-p e000 08:03 845424 /usr/lib/libXext.so.6.4.0 b7f2c000-b8016000 r-xp 08:03 845806 /usr/lib/libX11.so.6.2.0 b8016000-b8017000 ---p 000ea000 08:03 845806 /usr/lib/libX11.so.6.2.0 b8017000-b8018000 r--p 000ea000 08:03 845806 /usr/lib/libX11.so.6.2.0 b8018000-b801a000 rw-p 000eb000 08:03 845806 /usr/lib/libX11.so.6.2.0 b801a000-b801b000 rw-p b801a000 00:00 0 b801f000-b8021000 rw-s fc68 00:0f 7044 /dev/nvidia0 b8021000-b8031000 rw-s fc61 00:0f 7044 /dev/nvidia0 b8031000-b8033000 rw-s fc601000 00:0f 7044 /dev/nvidia0 b8033000-b8034000 rw-s fc10 00:0f 7044 /dev/nvidia0 b8034000-b8035000 rw-s fc101000 00:0f 7044 /dev/nvidia0 b8035000-b8037000 rw-p b8035000 00:00 0 b8037000-b8038000 r-xp b8037000 00:00 0 [vdso] b8038000-b8054000 r-xp 08:03 1350300/lib/ld-2.9.so b8054000-b8055000 r--p 0001b000 08:03 1350300/lib/ld-2.9.so b8055000-b8056000 rw-p 0001c000 08:03 1350300/lib/ld-2.9.so bfd41000-bfd56000 rw-p bffeb000 00:00 0 [stack] Aborted -- Stack Smashing Prevents Use https://bugs.launchpad.net/bugs/72117 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
*Should I fill in new bug report? -- Stack Smashing Prevents Use https://bugs.launchpad.net/bugs/72117 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
I have the same problem with Jaunty (nvclock 0.8b4-1ubuntu2) -- Stack Smashing Prevents Use https://bugs.launchpad.net/bugs/72117 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
The problem still seems to be an issue for me. $ uname -a: Linux falcon-2 2.6.20-16-lowlatency #2 SMP PREEMPT Wed May 23 01:49:41 UTC 2007 i686 GNU/Linux -- Stack Smashing Prevents Use https://bugs.launchpad.net/bugs/72117 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
** Changed in: nvclock (Ubuntu) Status: Fix Committed = Fix Released -- Stack Smashing Prevents Use https://launchpad.net/bugs/72117 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
I confirm that latest nvclock package (0.8b2-1ubuntu1) solved the problem in my Feisty amd64. -- Stack Smashing Prevents Use https://launchpad.net/bugs/72117 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
nvclock (0.8b2-1ubuntu1) feisty; urgency=low * Hack in dpatch. * Use patch from Andreas Simon to fix buffer overflow. (LP: #72117) * Update Maintainer address. -- Steve Kowalik [EMAIL PROTECTED] Tue, 13 Mar 2007 16:23:34 +1100 ** Changed in: nvclock (Ubuntu) Status: Confirmed = Fix Committed -- Stack Smashing Prevents Use https://launchpad.net/bugs/72117 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
Here is a debdiff which fixes the issue here. In src/backend/back_linux.c I changed the line if(sscanf(buffer,%s %d %d,name, size, used) != 3) continue; to if(sscanf(buffer,%19s %d %d,name, size, used) != 3) continue; to prevend a overflow of name[]. I attached a debdiff and will also notify upstream about this issue. ** Attachment added: Debdiff http://librarian.launchpad.net/6652708/nvclock_0.8b2-1.debdiff -- Stack Smashing Prevents Use https://launchpad.net/bugs/72117 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
** Tags added: patch -- Stack Smashing Prevents Use https://launchpad.net/bugs/72117 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
** Changed in: nvclock (Ubuntu) Assignee: ville palo = (unassigned) Status: In Progress = Confirmed -- Stack Smashing Prevents Use https://launchpad.net/bugs/72117 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
If you are asking me: cpufreq_conservative 8712 0 - Live 0xf8b07000 Is longest having just 20 chars, no more. -- Stack Smashing Prevents Use https://launchpad.net/bugs/72117 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
Thanks! 20 chars + NULL char is enough to crash the stack: from back_linux.c (buffer contains line from /proc/modules) char name[20]; int size; int used; /* Check to see if NVdriver/nvidia is loaded and if it is used. / For various versions the driver isn't initialized whe n X hasn't / been started and it can crash then. */ if(sscanf(buffer,%s %d %d,name, size, used) != 3) continue; ** Changed in: nvclock (Ubuntu) Status: Confirmed = In Progress -- Stack Smashing Prevents Use https://launchpad.net/bugs/72117 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
Thanks, I got it working by _dirty_ little trick:
As I know I am always using nvidia driver, so I changed whole function to:
static int check_driver() {return 2; //driver nvidia}
Re-compiled no more stack smashing. I also tried to increase char
name[20] size, but somehow it didn't work.
I am happy now, my Asus 7300 GT with heatsink runs very hot, so this was
very important to me. Thanks again.
--
Stack Smashing Prevents Use
https://launchpad.net/bugs/72117
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
Please, could you check your /proc/modules file? Is there some modules with a name longer than 20 charachters? -- Stack Smashing Prevents Use https://launchpad.net/bugs/72117 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
** Changed in: nvclock (Ubuntu) Importance: Undecided = Medium Assignee: (unassigned) = ville palo Status: Unconfirmed = Confirmed -- Stack Smashing Prevents Use https://launchpad.net/bugs/72117 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
This happens every single time with nvclock 0.8b2 on my fresh Edgy install (and I am pretty sure it also did it with my previous Dapper install). For reproducing, have a (Asus) GF 7300 (GT), download source from http://www.linuxhardware.org/nvclock/, ./configure make make install nvclock -s. Maybe this has somtething to do with Ubuntu, because google finds this problem only from Ubuntu users. This didn't happen with 0.8b1 (version in Edgy repositories), but it's maybe because that version doesn't even support my Asus GF 7300 GT, so it didn't work either. (nvclock -s gives some random negative speeds like -123402 Mhz). -- Stack Smashing Prevents Use https://launchpad.net/bugs/72117 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
see previous comment ** Attachment added: backtrace of nvclock 0.8b2 crashing http://librarian.launchpad.net/5629265/gdb-nvclock.txt -- Stack Smashing Prevents Use https://launchpad.net/bugs/72117 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
With current 2.6.20-4 kernel, it happens reliably. [EMAIL PROTECTED]:/home/justin# uname -a Linux justin01 2.6.20-4-generic #2 SMP Fri Jan 5 04:31:55 UTC 2007 i686 GNU/Linux [EMAIL PROTECTED]:/home/justin# nvclock -s *** stack smashing detected ***: nvclock terminated Aborted (core dumped) -- Stack Smashing Prevents Use https://launchpad.net/bugs/72117 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
Woops. Seems that a reboot fixes the issue. My suggestion is that whatever flag be set in order to have the Update Notification applet indicate that a reboot is necessary. -- Stack Smashing Prevents Use https://launchpad.net/bugs/72117 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72117] Re: Stack Smashing Prevents Use
I was not able to reproduce on my edgy, could you please attach the crash dump/backtraces, instructions can be found here: https://wiki.ubuntu.com/DebuggingProgramCrash -- Stack Smashing Prevents Use https://launchpad.net/bugs/72117 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
