Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 86933 - ddd unstable debugging large Fortran code
Summary: ddd unstable debugging large Fortran code
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: AMD64 Linux
: High major (vote)
Assignee: Martin Holzer (RETIRED)
URL:
Whiteboard:
Keywords:
: 116886 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-03-27 22:16 UTC by Fred Krogh
Modified: 2006-10-05 15:16 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fred Krogh 2005-03-27 22:16:24 UTC
I think the problem is in ddd since gdb (which I'm clumsy at using) seems quite stable.  ddd frequently crashes.  I'm sorry that I don't have anything more useful to point at, but I'm willing to supply more detail if I know what would be useful.
Probably not relevant, but when ddd starts it puts up an error window saying

"/var/tmp/portage/glibc-2.3.4.20050125-41/work/build-default-x86_64-pc-linux-gnu-linuxthreads/csu/crti.S:No such file or directory"

This is version 3.3.10 of DDD, compiled with gcc 3.4.3-20050110.


I'd be happy to help if I have some idea of what would be useful.
I should note that I'm using masked versions of gcc and glibc.  With the unmasked versions things are much worse.





Reproducible: Always
Steps to Reproduce:
Although it always crashes, it crashes in different places on different runs.




Portage 2.0.51.19 (default-linux/amd64/2004.3, gcc-3.4.3-20050110,
glibc-2.3.4.20050125-r1, 2.6.10 x86_64)
=================================================================
System uname: 2.6.10 x86_64 AMD Opteron(tm) Processor 242
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 28 2005, 20:08:50)]
ccache version 2.3 [enabled]
dev-lang/python:     2.3.4-r1
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.5, 1.8.5-r3, 1.6.3, 1.7.9-r1, 1.4_p6, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r1
sys-devel/libtool:   1.5.10-r4
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CFLAGS="-march=opteron -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env
/usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config
/usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=opteron -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox"
GENTOO_MIRRORS="http://gentoo.osuosl.org/ http://adelie.polymtl.ca/
ftp://cs.ubishops.ca/pub/gentoo http://csociety-ftp.ecn.purdue.edu/pub/gentoo/
http://gentoo.seren.com/gentoo ftp://linux.cs.lewisu.edu/gentoo/
http://mirror.usu.edu/mirrors/gentoo/"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"
USE="X acpi alsa amd64 apache2 atlas bash-completion bcmath bitmap-fonts bonobo
cups curl doc emacs esd f77 fam fastcgi fbcon font-server fortran gdbm gif gnome
gphoto gpm gstreamer gtk gtk2 icq imlib ipv6 java javascript jikes jp2 jpeg leim
libwww lzw lzw-tiff motif mozilla mp3 mysql mysqli ncurses nls ofx oggvorbis
opengl oss pam pcmica perl png prp python qt readline samba sasl session shared
sharedmem sml2 sockets ssl symlink tcpd tetex threads tiff truetype
truetype-fonts type1-fonts usb userlocales xemacs xml2 xmms xpm xprint xrandr xv
zlib"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Comment 1 Fred Krogh 2005-03-27 22:25:04 UTC
Forgot to mention that when running ddd my hardware monitor is showing a lot of network traffic, which ends as soon as ddd is killed (after dying).
Comment 2 Fred Krogh 2005-03-28 08:37:07 UTC
Scratch that comment about the network.  The order of things in the hardware monitor and gotten exchanged.  Sorry.
Comment 3 Justace Clutter 2005-07-06 20:01:08 UTC
I am having similar problems but on x86.

Has there been a fix for this yet?
Comment 4 Fred Krogh 2005-07-06 20:50:59 UTC
Nohting new on this.  I might mention that ddd tends to crash when moving the
mouse cursor in the source window.  I'm not sure that it ever crashes when moved
in debugger console or data windows.  Also I think I've only had the problem
with Fortran source.  (I am not currently doing much in C.)
Comment 5 Fred Krogh 2005-12-02 17:54:55 UTC
Just to keep this a little more up to date.  I'm now on version 3.3.11 of ddd,
glibc-2.3.5-r3,and gcc-3.4.4-r1.  The error message when starting now says

/var/tmp/portage/glibc-2.2.5-r3/work/build-amd64-x86_64-pc-linux-gnu-linuxthreads/csu/crti.S:
No such file or directory.

It would seem that fixing this diagnostic or giving instructions on how to avoid
it should not be a big deal for someone who understands how this all works.  (I
do realize that such might be a rare beast.) Perhaps with this fixed the other
problem would go away.  I'm wondering if something like the patch at

http://forums.gentoo.org/viewtopic-t-376943.html

is something that might be needed.  (I'm not going to much with glibc unless
I've got a very good reason.)
Comment 6 Fred Krogh 2005-12-26 09:47:23 UTC
The problem appears to be fixed on my machine.  I had use flags for motif and lesstif.  I removed lesstif from my use flags and re-emerged ddd.  It no longer seems to crash when moving the cursor in the source window of Fortran codes.  Perhaps motif should be required with ddd?
Comment 7 Jakub Moc (RETIRED) gentoo-dev 2005-12-27 08:27:33 UTC
*** Bug 116886 has been marked as a duplicate of this bug. ***
Comment 8 Jakub Moc (RETIRED) gentoo-dev 2005-12-27 08:27:50 UTC
Reopen.
Comment 9 Fred Krogh 2006-02-12 08:45:46 UTC
I don't know why it has taken me so long to notice this, but it appears that what makes the code crash is to move the cursor in the source window over a dummy array.  Other dummy arguments cause no problem.  Perhaps this will suggest where the problem is?  Many thanks.
Comment 10 Fred Krogh 2006-02-19 12:45:43 UTC
I have posted this to the ddd bugs on the ddd home site with full details, but it may be of interest here.  Below is a very short Fortran code.  If you run it in ddd, set a break on the next to last line, then move the mouse cursor over the array II then ddd will crash every time.  (Or at least it does for me.)

c Program to show problem in ddd
      integer I, IA(5)
      call sub1(IA)
      print *, (IA(I), I = 1, 5)
      stop
      end
      subroutine sub1(II)
      integer I, II(*)
      do 10 I = 1, 5
        II(I) = I
 10   continue
      return
      end
Comment 11 Fred Krogh 2006-10-05 15:16:27 UTC
Sorry, I should have mentined this awhile back.  This problem is gone when using the new Fortran compiler. I'm now using GNU Fortran 95 (GCC) 4.1.1 (Gentoo 4.1.1-r1).  I've changed the status to FIXED although I'm not sure that is the right term.  There is no choice for "No longer relevent".