[SOLVED] Re: emacs23 not working in terminal
On 04/08/13 18:33, Ashish SHUKLA wrote: Where should I start looking? Start with truss(1)-ing the Emacs process. Hello. I trussed emacs... that was easy... Much harder is to extract something useful from the 1.1MB output: I give up on this, it's too hard without a pointer. If anyone is interested, I can upload the file somewhere. Anyway, I fixed this by choosing XAW over GTK in the port configuration. bye Thanks av. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: emacs23 not working in terminal
On 04/08/13 18:33, Ashish SHUKLA wrote: Are you able to reproduce it with: emacs -Q -nw ? No. Depending on the terminal I use, what I type might appear *after* I kill emacs. I solved this on most installations with portupgrade -Rf emacs, but I still have one box where this did not help. You mean upgrading to Emacs24 fixed it ? No, I mean reinstalling the same Emacs (23 or 24) and all dependencies fixed it somewhere (but not everywhere). Where should I start looking? Start with truss(1)-ing the Emacs process. I'll give it a shot, altough I'm a newbye with this... bye Thanks av. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
emacs23 not working in terminal
Hello. I'm a long time user of Emacs and I've got several different installations. Recently some of them started behaving: X11 version works fine, but running with -nw (or no X configured) results in keyboard not working. Pressing any key yields no result and emacs has to be killed externally. This happens regardless of how the box is accessed (local/ssh, Konsole/putty, etc...) I solved this on most installations with portupgrade -Rf emacs, but I still have one box where this did not help. Where should I start looking? bye Thanks av. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: emacs23 not working in terminal
On Mon, 08 Apr 2013 12:14:33 +0200, Andrea Venturoli m...@netfence.it said: Hello. I'm a long time user of Emacs and I've got several different installations. Recently some of them started behaving: X11 version works fine, but running with -nw (or no X configured) results in keyboard not working. Pressing any key yields no result and emacs has to be killed externally. This happens regardless of how the box is accessed (local/ssh, Konsole/putty, etc...) Are you able to reproduce it with: emacs -Q -nw ? I solved this on most installations with portupgrade -Rf emacs, but I still have one box where this did not help. You mean upgrading to Emacs24 fixed it ? Where should I start looking? Start with truss(1)-ing the Emacs process. HTH -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 Sent from my Emacs pgpmZhgDh9agM.pgp Description: PGP signature
Re: emacs23
On 09/23/12 00:21, Ashish SHUKLA wrote: Hi Andrea, I don't use GDB integration of Emacs to notice any breakage. Could you post here (or on emacs-devel[1] list) about problems you're facing, and if reproducible by others as well, then we can probably file a bug report on Emacs bug tracker[2]. I'll post here, since I don't know whether this is a FreeBSD specific problem. The box is running 8.3/i386 (but on 9.0 it's the same). The problem is quite complex, meaning so many things are just screwed up that you end up wondering if this is production ready software. I'll try to explain with an example session, which I hope will show some of the bugs of the new version; I'm open to feedback in case something is not clear. %emacs M-x gdb (I'm prompted with gdb -i=mi and just add the executable name). (I get This version of GDB doesn't support non-stop mode. Turnig it off; I don't know what this means, I just ignore it.) b main r (I get argc=Error accessing memory address 0x0: Bad address.) p argc (I get Error accessing memory address 0x0: Bad address.) (Ok, so I cannot look into a variable). frame (I'd expect to see the source, but I don't). C-x C-f and I open the source manually. (Positioned on the source line I want a breakpoint on) C-x Space (The dot appears grey, not red, as tough the source was not recognized; however the breakpoint seems to work). r (The program starts and stops at the first breakpoint; however I get no indication of this in the source window). n (Nothing happens, the pointer in the source does not move, in *gud* windows the same line is reported) n (Nothing happens, the pointer in the source does not move, in *gud* windows the same line is reported) n (Debugger segmentation fault: 11 (core dumped)) Ok, I give up with gdb from base and try gdb75 from ports. M-x gdb (I'm prompted with gdb -i=mi, add the executable name and substitute gdb with /usr/local/bin/gdb75). b main r n (Things work better here; I get an *input/output* windows I cannot get rid of) c After a while C-c C-c (The program stops in write from the runtime outside my program) frame (gdb locks up) %kill gdb75 M-x gdb The program is already being debugged C-x C-k M-x gdb (I'm prompted with gdb -i=mi, add the executable name and substitute gdb with /usr/local/bin/gdb75). (Ok this time) r After a while C-c C-c (The program stops in read from the runtime outside my program) (avoiding the use of frame, which produced a lockup earlier) bt frame 7 (now in my program) I move to the next line and give C-x Space (nothing happens; from now on I cannot insert breakpoints this way) b foo.cxx:45 (manual insert of breakpoint works) fin fin fin fin fin fin n (program moves correctly to the next line) (I lose (gdb) prompt, so I have an hard time trying to tell what I wrote from what the debugger wrote; also if I leave the window for a while, when I'm back I have to guess whether the program is running or stopped) b 'functab' (gdb locks up; eventually emacs locks too and I have to quit it or kill it). This is of course only an example, but it shows most of the ways in which I found emacs24+gdb can fail or annoy. I suspect there are others. Since it cannot be pinpointed to a single bug, I guess either some version incompatibility or some wrong compilation option, but I really don't know where to look. And, as for the security vulnerability which I forgot to fix for editors/emacs23 (my fault, apologies), I'm testing a fix[3] in tinderbox, once it builds fine, I'll commit it. Thanks for this. bye av. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
emacs23
Hello. What are the plans for emacs23? It is marked as vulnerable now, but emacs24 is almost unusable (1)... bye Thanks av. (1) I'm mainly referring to gdb integration: in case anyone is interested, I can describe some of the problems. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: emacs23
On Sat, Sep 22, 2012 at 1:47 PM, Andrea Venturoli m...@netfence.it wrote: Hello. What are the plans for emacs23? It is marked as vulnerable now, but emacs24 is almost unusable (1)... bye Thanks av. (1) I'm mainly referring to gdb integration: in case anyone is interested, I can describe some of the problems. Did you asked about that in emacs development list (emacs-de...@gnu.org)? -- Andrew W. Nosenko andrew.w.nose...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: emacs23
On Sat, 22 Sep 2012 12:47:31 +0200, Andrea Venturoli m...@netfence.it said: Hello. What are the plans for emacs23? It is marked as vulnerable now, but emacs24 is almost unusable (1)... bye Thanks av. (1) I'm mainly referring to gdb integration: in case anyone is interested, I can describe some of the problems. Hi Andrea, I don't use GDB integration of Emacs to notice any breakage. Could you post here (or on emacs-devel[1] list) about problems you're facing, and if reproducible by others as well, then we can probably file a bug report on Emacs bug tracker[2]. And, as for the security vulnerability which I forgot to fix for editors/emacs23 (my fault, apologies), I'm testing a fix[3] in tinderbox, once it builds fine, I'll commit it. References: [1] https://lists.gnu.org/mailman/listinfo/emacs-devel/ [2] http://debbugs.gnu.org/Emacs.html [3] http://people.freebsd.org/~ashish/diffs/emacs23.4_1%2c1.diff Thanks -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 Sent from my Emacs pgpFas4rAjTEf.pgp Description: PGP signature
