From: Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
To: gdb@sourceware.org
Subject: Problems while debugging fortran
Date: Sat, 15 Sep 2007 11:37:00 -0000 [thread overview]
Message-ID: <46EB035B.4090802@linux.vnet.ibm.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello
I'm having some trouble while debugging this code:
c-------------------
c test.f
c ------------------
program this
i=ifunc(1)
print *,i
end
function ifunc(i)
print *,i*2
ifunc = 1
return
end
c ------------------
If I try to set a breakpoint by line number, gdb displays:
No line xx in file "init.c"
However, it works if I set the breakpoint by function name (e.g. "break
this"). If I run the program, then clear all breakpoints and try to set
a breakpoint by line number, it'll work IF the line is within the scope
of that function (i.e. if I set "break this", I can't set a breakpoint
by line in the line "print *,i*2").
What I believe is that the psymtab does not contain either function
symbols, since it's behaving differently when the psymtab is read and
when the corresponding symtab is read in. That's why GDB cannot find the
lines (worse, it's looking for them in the wrong file).
Is that line of thought correct? Any ideas where I should start looking
for the problem?
Thanks and regards,
- --
Carlos Eduardo Seo
Software Engineer
IBM Linux Technology Center
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG6wNbqvq7Aov/qQARAq0OAJ0X+xgtyA7+MnPIJostKRmpY3iylACffdNc
/3EYMQfX7tINpGHt03i/Cqg=
=bvvo
-----END PGP SIGNATURE-----
next reply other threads:[~2007-09-14 21:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-15 11:37 Carlos Eduardo Seo [this message]
2007-09-20 19:47 ` Joel Brobecker
2007-09-20 20:46 ` Carlos Eduardo Seo
2007-09-20 20:56 ` Joel Brobecker
2007-09-21 6:52 ` Daniel Jacobowitz
2007-09-26 21:46 ` Carlos Eduardo Seo
2007-09-26 21:51 ` Pierre Muller
2007-09-26 21:51 ` Joel Brobecker
2007-10-24 16:20 ` Carlos Eduardo Seo
2007-10-24 19:33 ` Joel Brobecker
2007-10-24 19:57 ` Daniel Jacobowitz
2007-10-24 20:16 ` Carlos Eduardo Seo
2007-10-24 21:56 ` Carlos Eduardo Seo
2007-09-23 2:52 ` Carlos Eduardo Seo
2007-09-24 10:01 ` Joel Brobecker
2007-09-24 23:49 ` Carlos Eduardo Seo
2007-09-25 1:29 ` Joel Brobecker
2007-09-25 17:34 ` Carlos Eduardo Seo
2007-09-26 6:29 ` Joel Brobecker
2007-10-25 16:07 François-Xavier Coudert
2007-10-25 17:06 ` Daniel Jacobowitz
2007-10-25 18:44 ` Jim Blandy
2007-10-25 19:01 ` Daniel Jacobowitz
2007-10-25 19:27 ` Jim Blandy
2007-10-25 20:24 ` Joel Brobecker
2007-10-25 20:36 ` Carlos Eduardo Seo
2007-10-25 20:41 ` Joel Brobecker
2007-10-25 20:55 ` Andreas Schwab
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46EB035B.4090802@linux.vnet.ibm.com \
--to=cseo@linux.vnet.ibm.com \
--cc=gdb@sourceware.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox