FreeBSD Port: valgrind-snapshot-352_7
Hello, I am trying to use valgrind on fbsd 6.2 patch 7 to find a memory leak in an ecpg postgresql app. When I run valgrind after a few minutes I get this error and valgrind terminates. Ideas? PORTNAME= valgrind PORTVERSION=352 PORTREVISION= 7 CATEGORIES= devel valgrind: vg_malloc2.c:1008 (vgPlain_arena_malloc): Assertion `new_sb != ((void*)0)' failed. ==4166==at 0xB802BE1F: (within /usr/local/lib/valgrind/stage2) ==4166==by 0xB802BE1E: (within /usr/local/lib/valgrind/stage2) ==4166==by 0xB802BE5D: vgPlain_core_assert_fail (in /usr/local/lib/valgrind/stage2) ==4166==by 0xB8028091: vgPlain_arena_malloc (in /usr/local/lib/valgrind/stage2) sched status: Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 ==4166==at 0x3C03894B: calloc (in /usr/local/lib/valgrind/vgpreload_memcheck.so) Note: see also the FAQ.txt in the source distribution. It contains workarounds to several common problems. If that doesn't help, please report this bug to: valgrind.kde.org In the bug report, send all the above text, the valgrind version, and what Linux distro you are using. Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unhappy Xorg upgrade
Alex Goncharov wrote: ,--- You/Bruce (Thu, 29 Jan 2009 12:06:45 +) * | One theory is that somehow the mouse driver ioctls which are passed | to ums, are somehow hosing USB, although why that would be, I don't | understand. ums currently doesn't have driver instrumentation in that path. | | I pulled a fairly detailed IRC log of my collaborative debugging | session with Robert, please ping me if you need details of this. `* Thank you for the detailed write up! No help to me, though -- on my Latitude laptop, there was no problem with any mouse: USB or the built-in "pointing device". It was the keyboard -- and, trust me, I did try many variations of the machine configuration, and I did do a lot of reading on various relevant topics (writing, too, as you have seen :-() As I mentioned elsewhere, my way of resolving the problem after a one-and-a-half day's of struggle was to revert to the old X (on that laptop). On the topic of how this upgrade was introduced, I can't help but refer to my recent experience helping to fix TWM: ,--- Eeri Kask (Mon, 29 Sep 2008 12:21:17 +0200) * | > I have used the new version of TWM for five days, using it less | > intensively than usual. No problems in seen during my (light) use. | | Hello Alex, no problem at all! Improved solutions have priority over | promised deadlines. | | Thank you for your time helping to improve TWM, :-) | `* Eeri Kask and I worked together all past September on fixing TWM crashes: I was willingly trying his multiple versions of the code, but I knew what I was risking, could choose convenient times for building and trying every new version (we tried about 30 of them) -- and I could always go back to the previous version (or the original TWM from ports). I would be happy to try a new X on my machines, if it were labeled as experimental, with an easy way to revert to the old X (while being in the testing stage). As it is, this upgrade brought a lot of problems to unsuspecting people, at the time they don't quite choose, with potential dangers not disclosed. In honesty, this upgrade should have been presented this way, way before the code was placed in the ports source tree: * We'll have a new X in ports soon -- there are multiple reports of problems with it on Linux. * We want to try it on FreeBSD -- but nobody is forcing you to do the upgrade. * If you, of your own free will, choose to upgrade, you may have hours and days of problems -- but heck, it was your choice. * If your problems cannot be fixed, you'll have to figure out something yourself. * If you choose not to upgrade, you are frozen with the pre-existing ports collection: there may be no automated ways to upgrade your packages, with the old X in place. Of course, you can somehow get pieces on new ports, unrelated to X. * The choice is totally yours. -- Alex -- alex-goncha...@comcast.net -- ___ freebsd-sta...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" On my system the matrox driver quit working, when I tried using the built in via the via driver wouldn't compile so when I tried X -configure it generated a config using vesa, but when I tried to start X with the xorg.conf.new with the vesa driver X said it couldn't find any screens. I finally had to revert back to an older version. This should not happen on a stable system. -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Unhappy Xorg upgrade
Dan Allen wrote: Thanks to Robert for pointing out a few things to me. I have run portupgrade -rf libxcb I normally run portupgrade -WrRpPa This is what I ran and it totally hosed my system. I had to revert back to an earlier version to be able to bring X back up. This should have compiled and built everything that was affected by the new X stuff - but it obviously didn't. and it rebuilt quite a few pieces that had not been rebuilt in the standard portupgrade that gave me X.org 7.4 in the first place. After rebuilding firefox and a bunch of smaller libraries, my keyboard and mouse work, and so does firefox and my other apps. Thanks to everyone else for emailing me with ideas and suggestions! Dan ___ freebsd-sta...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Unhappy Xorg upgrade
Alex Goncharov wrote: ,--- You/Peter (Sat, 31 Jan 2009 06:53:11 +1100) * | X11 is a critical component for anyone who is using FreeBSD as a | desktop and having upgrades fail or come with significant POLA | violations and regressions for significant numbers of people is not | acceptable. Fully agree with this. | I suggest that this approach needs to be followed for every future | release of X.org until (if) the X.org Project demonstrates that they | can provide release-quality code. And agree with this, as far as the future is concerned -- but this leaves out the issue of what is going to be done for people whose systems became practically incapacitated in a matter of one day. Screw us? I realize that personally I haven't contributed much (hey, a simple port's maintainer!) to FreeBSD, so a disregard to my situation may be well deserved. But "you" (whoever this "you" is: the "ports manager", the X port maintainers) have to be aware that leaving the things in the state they are now, you are screwing somebody. | > This update also brings in support for a lot of people who are | >running newer hardware. | | And breaks support for lots of people who used to have functional X | servers. Just so. ,--- Kostik Belousov (Fri, 30 Jan 2009 22:25:09 +0200) * | Just to give a different view on *this* update. I have exactly opposing | experience. | | So far 1.5.3 + updated DRM works good on all my Radeons. | And, I did not have a problem with i945GM on 1.4.2 and 1.5.3. `--* Well, glad for you -- meanwhile I will be reverting my desktop to the old X this weekend: the garbage on the screen is ugly, but the fact that in the new X "opera" can grab a pointer for about a minute makes the combined use of the browser and xterms/Emacses plain intolerable. After I do this, as I did with my laptop already, I think I am completely cut off from the ports automated upgrade cycle. -- Alex -- alex-goncha...@comcast.net -- ___ freebsd-sta...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" To add my experience, I have been using X on intel hardware since the late eighties when you had to calculate your modeline by hand. But I guess I have gotten spoiled by how easily it now is to normally configure X. Run X -configure and you normally are good to go. Well at work I had a dual head matrox card that would not configure after the upgrade, so I took it out of the machine to use the built in via graphics controller that worked fine under 1.4 but when I ran X -configure there was an error trying to load the via driver, because it didn't compile ( and as I later found out has been replaced by the openchrome driver - didn't see anything about that in UPDATING ) so the automatic config fell back to using the vesa driver. But when I tried to run X -config /root/xorg.conf.new X reported it couldn't find any screens for vesa driver no matter how I changed the config. After fighting with this for half a day I reverted back to 1.4 because I needed my machine operational to get some work done. -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
