unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: robert marshall <robert.marshall@tnei.co.uk>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: 23.0.60; gdb not running the program first time around
Date: Mon, 18 Feb 2008 09:32:27 +0000	[thread overview]
Message-ID: <47B950AB.6090603@tnei.co.uk> (raw)
In-Reply-To: <18358.1492.10000.208409@kahikatea.snap.net.nz>

Nick Roberts wrote:
>  > I've just tried
>  >     (setq gdb-many-windows t)
>  > - not used this before and apart from being faviourably impressed :-) 
>  > I've come across one problem.
>  > Our code tends to swap languages - top level is C++ which calls a c 
>  > layer which then invokes some fortran,
>  > when I get down to the fortran I get a debugger segmentation fault 
>  > immediately, I don't see this issue when gdb-many-windows is nil
>
> You're probably stretching the boundaries of Gdb a bit - it's not so good with
> C++ but it's getting better.  Also I've found that for fortran debugging, g77
> is better than gfortran as it currently generates better debug information.  I
> think gfortran is the future, however, and compiles fortran 95.
>
>   
As with other contributors to this thread I've found the c++ support to 
be fine - fortran appears dodgier.
We have some code which contains fortran linked lists where a points to 
b which points to c which points to a,
printing out a causes a loop I'll get a bug report sent when I can get 
an appropriate small example

>  > Do you want me to create a separate report for this - I assume there's a 
>  > couple of issues here a gdb one and a gdb-ui.el one?
>
> A debugger segmentation fault means a bug in Gdb, so the report should go to
> the gdb mailing list (gdb@sourceware.org).  Most users probably don't debug
> inside Emacs, so you really need to find a way to reproduce it from the
> command line.  Since it only happens with gdb-many-windows it is probably
> caused by one of the gdb commands that Emacs runs behind the user's back
> to update the extra buffers:
>
> info stack
> interpreter mi "-stack-list-locals --simple-values"
>
> If you can get to where the debugger segmentation fault occurs from the
> command line then issing these commands might trigger it.
>
>   
Is it possible to turn off the functionality of gdb-many-windows on the fly?
I think the bug I'm triggering may well be this one:
http://permalink.gmane.org/gmane.comp.gdb.bugs.discuss/4934
so I probably need to update gdb with a build from source

Robert

-- 
Robert A J Marshall,  
TNEI Services Ltd, 88-90 London Road, Manchester, M1 2PW 
Registered in England & Wales No. 03891836,
Registered office:  Milburn House, Dean Street, Newcastle upon Tyne, NE1 1LE
tel: +44 161 615 6017; fax: +44 161 615 6001; mobile: +44 7759 688384 
web: http://IPSA-Power.com 





  parent reply	other threads:[~2008-02-18  9:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 10:13 23.0.60; gdb not running the program first time around robert marshall
2008-02-14  0:33 ` Nick Roberts
2008-02-14  9:04   ` robert marshall
2008-02-14 23:01     ` Nick Roberts
2008-02-15 11:28       ` robert marshall
2008-02-15 21:36         ` Nick Roberts
2008-02-15 22:30           ` Miles Bader
2008-02-16 13:13             ` Eli Zaretskii
2008-02-18  9:32           ` robert marshall [this message]
2008-02-18 10:12             ` Nick Roberts
2008-02-21  9:31         ` robert marshall
2008-02-22  8:43           ` Nick Roberts

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47B950AB.6090603@tnei.co.uk \
    --to=robert.marshall@tnei.co.uk \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=nickrob@snap.net.nz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).