help-gnu-emacs
[Top][All Lists]
Advanced

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

Re: Strange font / frame size problem makes emacs unusable.


From: tomas
Subject: Re: Strange font / frame size problem makes emacs unusable.
Date: Mon, 26 Apr 2010 07:28:58 +0200
User-agent: Mutt/1.5.15+20070412 (2007-04-11)

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

On Sun, Apr 25, 2010 at 11:49:20PM +0200, Peter Dyballa wrote:
>
> Am 25.04.2010 um 21:43 schrieb Gaute Amundsen:
>
>> read(3, 0x9f10018, 4096)                = -1 EAGAIN (Resource
>> temporarily unavailable)
>> read(3, 0x9f10018, 4096)                = -1 EAGAIN (Resource
>> temporarily unavailable)
>
> What is there "temporarily unavailable?" And why at all?
>
>> poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3,
>> revents=POLLOUT}])
>> writev(3, [{"2\30\21\0\1\0<\0", 8},
>> {"-misc-fixed-medium-r-normal--161"..., 60}, {"", 0}], 3) = 68
>
>
> [...] Find and check them! Some trace variant is able to record files 
> being opened.

As Peter says, try to find what fd=3 is (somewhere higher in the trace
there should be a call to open/connect returning 3).

Linux makes it difficult to find the "other end" of a Unix domain
socket; nevertheless, if you say "ls -l /proc/fd/<pid of your Emacs>,
you'll see where fd3 is going to; with "lsof" or "netstat -axp" you'll
"see" the connection, but not which process is at the other end...

So your best bet is to search for connect/open/whatever other calls
might be returning an fd of 3 up your trace.

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFL1SSYBcgs9XrR2kYRAj87AJ9UzzO5F3MiXZS3V1EdmpFsXi+RHwCfdudj
chTp7MY0i9LdHamg5s8x98k=
=XkSW
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]