Midnight Commander Startup Bug



Using the source files for ORBit 0.3.97 and MC 4.5.13
The first time crash still apears.

Problem:
If you load X, then gmc, and hit the X (close) button on a gmc window, gmc
crashes. 
The second and all other times running gmc until you restart X, gmc doesnt
crash when hitting the close button.

I tryed to compile mc with the debug stuff but it dies with:
util.o: In function `get_current_wd':
util.o(.text+0x1098): the `getwd' function is dangerous and should not be
used.
util.o: In function `mad_strdup_vprintf':
util.o(.text+0x1b5f): undefined reference to `__va_copy'
make[1]: *** [mc] Error 1
make[1]: Leaving directory `/usr/src/redhat/BUILD/mc-4.5.13/src'
make: *** [all] Error 1
Bad exit status from /var/tmp/rpm-tmp.25396 (%build)

It compiles just fine without the debug stuff.

If I run gdb gmc and hit the close button, I get:
	[root@george /root]# gdb gmc
	[snip gdb license stuff]
	(no debugging symbols found)...
	(gdb) run
	Starting program: /usr/bin/gmc 
	(no debugging symbols found)...(no debugging symbols found)...
	(no debugging symbols found)...(no debugging symbols found)...
	GNU Midnight Commander 4.5.13

	GLib-CRITICAL **: file ghash.c: line 131 (g_hash_table_lookup):
assertion `hash_table != NULL' failed.

	GLib-CRITICAL **: file ghash.c: line 131 (g_hash_table_lookup):
assertion `hash_table != NULL' failed.

	GLib-CRITICAL **: file ghash.c: line 131 (g_hash_table_lookup):
assertion `hash_table != NULL' failed.

	GLib-CRITICAL **: file ghash.c: line 131 (g_hash_table_lookup):
assertion `hash_table != NULL' failed.

	** WARNING **: Getgroups should be used here


	Gdk-ERROR **: an x io error occurred
	aborting...
	(no debugging symbols found)...(no debugging symbols found)...
	Program received signal SIGABRT, Aborted.
	0x4044a811 in __kill ()
	(gdb) 


> -----Original Message-----
> From:	Miguel de Icaza [SMTP:miguel@nuclecu.unam.mx]
> Sent:	Thursday, February 11, 1999 6:47 AM
> To:	sri@aracnet.com
> Subject:	Re: Midnight Commander 4.5.13 is out
> 
> 
> > Oog.  I get the picture. :-)  Thats pretty lousy scaling, I agree.  I
> > guess, I'll look at the code and see what exactly is being done.
> 
> Well, right now we are using the gnome-mime functions.  There is
> gnome-mime fucntion that will determine the mime-type based on the
> contents of the file (so, it is just a matter of adding a new call and
> a number of config options).
> 
> Miguel.
> 
> 
> -- 
>         FAQ: Frequently-Asked Questions at http://www.gnome.org/gnomefaq
>          To unsubscribe: mail gnome-list-request@gnome.org with 
>                        "unsubscribe" as the Subject.



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