Re: More information on gnome executing problems

On Mon, 20 Jul 1998 rinckemd@RoseVC.Rose-Hulman.Edu wrote:

> Ok I've been getting the  
> ** ERROR **: could not allocate 134217728 bytes
> Abort
> problem on execution of ALL things gnome.
> I did a backtrace on the execution and this is what I fount:
> #0  0x4033e4c1 in __kill () at soinit.c:27
> #1  0x4033e31f in raise (sig=6) at ../sysdeps/posix/raise.c:27
> #2  0x4033f36e in abort () at ../sysdeps/generic/abort.c:83
> #3  0x400520bf in g_error (format=0x40058fa5 "could not allocate %ld
> bytes") at gmessages.c:64
> #4  0x4005178e in g_malloc (size=134217728) at gmem.c:125
> #5  0x4008f91e in gnome_client_init () at gnome-client.c:314
> #6  0x400a2348 in gnome_init (app_id=0x808a260 "panel",
> app_args=0x809e5f4, argc=2, argv=0xbffffa3c, flags=0, arg_index=0x0) at
> gnome-init.c:246
> #7  0x80525a7 in main (argc=2, argv=0xbffffa3c) at main.c:1911
> I'm still having problems figuring out exactly what the problem is:
> I'm running slack 3.5 with pgcc 1.0.3a and glibc-2.0.6.
> Can anyone tell from this where the problem is or what I can do get 
> more information about it?
> Miles

Ok, well it seems the getcwd is failing.  Isn't there some warning from
gcc about getcwd being dangerous and shouldn't be used.  I suspect that
getcwd always returns NULL and this is the problem.  I don't have the libc
sources and I am not about to D/L them via modem so I am at a loss as to
why getcwd fails.

Manish Vachharajani

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]