[Top][All Lists]

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

Re: Emacs fails parsing gdb output

From: Johan Walles
Subject: Re: Emacs fails parsing gdb output
Date: Thu, 12 Jul 2007 09:19:42 +0200

Thanks for the quick reply!

2007/7/12, Nick Roberts <address@hidden>:

> Using Emacs and GNU gdb 6.6-debian I have problems running gud.

You don't say what platform you're using.  If you use M-x report-emacs-bug, it
will give this detail and others about your configuration (and send to the
appropriate mailing list - address@hidden)

Sorry for that; i just followed the bug reporting guidelines at
http://www.gnu.org/software/emacs/.  Here's what report-emacs-bug
In GNU Emacs (i486-pc-linux-gnu, GTK+ Version 2.10.11)
of 2007-07-06 on helios
Windowing system distributor `The X.Org Foundation', version 11.0.70200000
configured using `configure  '--build' 'i486-linux-gnu' '--host'
'i486-linux-gnu' '--prefix=/usr' '--sharedstatedir=/var/lib'
'--libexecdir=/usr/lib' '--localstatedir=/var'
'--infodir=/usr/share/info' '--mandir=/usr/share/man' '--with-pop=yes'
'--with-x=yes' '--with-x-toolkit=gtk' '--enable-font-backend'
'--with-xft' '--with-freetype' 'build_alias=i486-linux-gnu'
'host_alias=i486-linux-gnu' 'CC=gcc' 'CFLAGS=-DDEBIAN

Important settings:
 value of $LC_ALL: nil
 value of $LC_COLLATE: nil
 value of $LC_CTYPE: nil
 value of $LC_MESSAGES: nil
 value of $LC_MONETARY: nil
 value of $LC_NUMERIC: nil
 value of $LC_TIME: nil
 value of $LANG: swedish
 value of $XMODIFIERS: nil
 locale-coding-system: iso-latin-1-unix
 default-enable-multibyte-characters: t

> GDB produces the attached output.

Does it fail with Emacs 22.1?

I'm having the same or very similar problems on Solaris / Sparc using
Emacs 22.1 and gdb-6.5.

> Emacs fails to parse all the annotations and says things like:
> "
> error in process filter: gdb-display-source-buffer: Wrong type
> argument: stringp, nil
> error in process filter: Wrong type argument: stringp, nil
> "

> It also fails to open the source code frame.

Can you please evaluate

(setq gdb-enable-debug t)

do M-x gdb

and start your application to generate the errors

then post the value of gdb-debug-log to address@hidden

Attached.  Since this (or something very similar) is a problem with
both 22.1 and I'm posting to both bug lists.

 Regards //Johan

Attachment: gdb-debug-log.txt
Description: Text document

reply via email to

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