Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GLib-ERROR **: gmem.c:175: failed to allocate 18446744073709551615 bytes #2023

Closed
mc-butler opened this issue Feb 13, 2010 · 8 comments
Closed
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress res: invalid The ticket is not a bug, or is a support request ver: 4.7.0.2 Reproducible in version 4.7.0.2
Milestone

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/2023
Reporter lvv (@lvv)
Keywords glib, 64

I see this error with mc-4.7.0.2 on gentoo x86_64. I've tied on/off all use flags and to compile from source. Error always the same.

~> uname -a
Linux ahp 2.6.30.9 #2 SMP Sun Jan 31 21:47:23 EET 2010 x86_64 Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz GenuineIntel GNU/Linux

~> eix dev-libs/glib
dev-libs/glib

Installed versions: 1.2.10-[5](1)(11:53:42 PM 06/14/2009)(-hardened)

2.22.4(2)(09:55:46 PM 01/29/2010)(doc fam -debug -hardened -selinux -xattr)

~> ldd /usr/local/bin/mc

linux-vdso.so.1 => (0x00007fffc8dff000)
libgpm.so.1 => /lib/libgpm.so.1 (0x00007f1b4b4f7000)
libslang.so.2 => /usr/lib/libslang.so.2 (0x00007f1b4b172000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x00007f1b4af6e000)
libdl.so.2 => /lib/libdl.so.2 (0x00007f1b4ad6a000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f1b4aa72000)
libc.so.6 => /lib/libc.so.6 (0x00007f1b4a719000)
libncurses.so.5 => /lib/libncurses.so.5 (0x00007f1b4a4c3000)
libm.so.6 => /lib/libm.so.6 (0x00007f1b4a240000)
/lib64/ld-linux-x86-64.so.2 (0x00007f1b4b6fe000)

~> l /usr/lib/libglib-2*
-rw-r--r-- 1 root root 1.8M 2010-01-29 21:55 /usr/lib/libglib-2.0.a
-rw-r--r-- 1 root root 953 2010-01-29 21:55 /usr/lib/libglib-2.0.la
lrwxrwxrwx 1 root root 23 2010-01-29 21:55 /usr/lib/libglib-2.0.so -> libglib-2.0.so.0.2200.4*
lrwxrwxrwx 1 root root 23 2010-01-29 21:55 /usr/lib/libglib-2.0.so.0 -> libglib-2.0.so.0.2200.4*
-rwxr-xr-x 1 root root 989K 2010-01-29 21:55 /usr/lib/libglib-2.0.so.0.2200.4*

Note

Original attachments:

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Feb 13, 2010 at 9:19 UTC (comment 1)

Please desrcibe step-by-step how to reproduce this bug.

@mc-butler
Copy link
Author

Changed by lvv (@lvv) on Feb 13, 2010 at 9:52 UTC (comment 1.2)

I just type "mc" at command prompt, press enter and immediately see this error. Reproducible always.

~> mc

GLib-ERROR : gmem.c:175: failed to allocate 18446744073709551615 bytes

aborting...

Aborted

@mc-butler
Copy link
Author

Changed by lvv (@lvv) on Feb 13, 2010 at 10:07 UTC (comment 3)

BTW:

~> wcalc -h 18446744073709551615

0xffffffffffffffff

@mc-butler
Copy link
Author

Changed by slyfox (@trofi) on Feb 13, 2010 at 11:07 UTC (comment 2.4)

Replying to lvv:

I just type "mc" at command prompt, press enter and immediately see this error. Reproducible always.

~> mc

GLib-ERROR : gmem.c:175: failed to allocate 18446744073709551615 bytes

aborting...

Aborted

My setup is mostly the same, but I use git ebuild and don't see such problems. Maybe, something like old ~/.mc/ content makes mc upset. You might try to verify it by moving temporarily ~/.mc/ somewhere, then rollback and proceed further investigation.
Maybe, it will be enough to send us contents of ~/.mc/.

Wonder, if -git one breaks for you. (In case you'll give it a try: http://www.midnight-commander.org/browser/contrib/dist/gentoo/README)

Would be nice to see whole stack trace for this breakage (might need to reemerge mc with FEATURES=debug). Either by attaching gdb:

$ gdb mc
> bt full

or by tracing it with valgrind:

$ valgrind --log-file=a.log --track-origins=yes mc

Thanks!

@mc-butler
Copy link
Author

Changed by lvv (@lvv) on Feb 13, 2010 at 19:34 UTC (comment 4.5)

It was .mc/ini
It has extranious line having just "======" - leftover from SVN merge.
Thanks for suggestion and troubleshooting.

@mc-butler
Copy link
Author

Changed by slyfox (@trofi) on Feb 14, 2010 at 11:08 UTC (comment 5.6)

Replying to lvv:

It was .mc/ini
It has extranious line having just "======" - leftover from SVN merge.
Thanks for suggestion and troubleshooting.

Tried to add ====== at the beginning of ini file and at the section start. Unable to reproduce failure. May I ask you to attach your ini file to this bug?

@mc-butler
Copy link
Author

Changed by lvv (@lvv) on Feb 14, 2010 at 11:51 UTC

".mc/" dir where "ini" file have extraneous "======"

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Mar 17, 2010 at 8:38 UTC (comment 7)

  • Resolution set to invalid
  • Status changed from new to closed

I believe it is a bug of GLib, not MC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress res: invalid The ticket is not a bug, or is a support request ver: 4.7.0.2 Reproducible in version 4.7.0.2
Development

No branches or pull requests

1 participant