-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ted Ozolins wrote:

> 
> Since I have both Gnome and KDE installed on this box (AMD 2G xp) and
> had not done an upgrade for about four months, just about every lib.
> glibc was one of the upgrades. I have gone through just about all the
> progs I use and do not have any problems with any of them aside from
> gtksee. I unmerged gtksee and deleted /home/ted/.gtksee then emerged
> gtksee with no change.  The two programs that I've had problems with in
> the past after an upgrade (pikdev, ponyprog) are unaffected this time. I
> haven't had time to really trace the prob nor check all bug reports
> (work load due to a new project at work is taking up just about all my
> time these days)

Basically, glibc is telling you that the application you're running (or a
library that it uses) passed free() an invalid pointer.

Where as with your previous version of glibc, the default action was to ignore
such things (unless a certain env var is set), for some reason the default
action of your present glibc is to display that message and abort().  I
somewhat remember this being fixed but I cannot say so with certainty.

Really it's the application's problem.  The best thing to do would be to try
and get a useful gdb backtrace and send it upstream (whether it's the app or a
lib it uses).  If you don't know how to get a backtrace, let me know.

Cheers
- --
Once I finally figured out all of life's answers, they changed the questions.

Aaron Walker <[EMAIL PROTECTED]>
[ BSD | cron | forensics | shell-tools | commonbox | netmon | vim | web-apps ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCe5WdC3poscuANHARAkVwAKCsvALvD8T4dP7vWoBmPc0GWXPwzwCgplhq
qJC/1WMBcB5d9e9dera3UOw=
=6pqQ
-----END PGP SIGNATURE-----
-- 
[email protected] mailing list

Reply via email to