public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: Problems while debugging fortran
Date: Sun, 23 Sep 2007 02:52:00 -0000	[thread overview]
Message-ID: <46F5D13D.2070303@linux.vnet.ibm.com> (raw)
In-Reply-To: <20070920204622.GB4368@adacore.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Joel Brobecker wrote:
>
> It should be the same if the "current file" is set to test.f.
> It looks like it isn't. For some reason, GDB thinks that the current
> file is something else. Again, perhaps a copy of your GDB session
> might give a clue.
>
Here's a sample output with some comments:

(gdb) b 25
No line 25 in file "init.c".
(gdb) b this
Breakpoint 1 at 0x10000670: file /tst111/ptr/fxdb1251.f, line 25.
(gdb) b 31
No line 31 in file "init.c".
(gdb) b ifunc
Breakpoint 2 at 0x10000770: file /tst111/ptr/fxdb1251.f, line 30.

As you can see, breakpoints by line number don't work. However, if I
use the function name, it works correctly.
At this point, if I clear all breakpoints and try to set them again by
line number, it doesn't work. Now, if I run the program, this happens:

(gdb) r
Starting program: /home/cseo/gdb-bugs/pr36275/fxdb1251
[Thread debugging using libthread_db enabled]
[New Thread 0xf7fb9000 (LWP 16185)]
[Switching to Thread 0xf7fb9000 (LWP 16185)]

Breakpoint 1, this () at /tst111/ptr/fxdb1251.f:25
25              i=ifunc(1)
Current language:  auto; currently fortran
(gdb) c
Continuing.

Breakpoint 2, ifunc (i=
During symbol reading, incomplete CFI data; unspecified registers
(e.g., r0) at 0x100007dc.
1) at /tst111/ptr/fxdb1251.f:30
30              print *,i*2
(gdb) c
Continuing.
 2
 1

Program exited normally.
(gdb) del
Delete all breakpoints? (y or n) y
(gdb) b 25
Breakpoint 3 at 0x10000670: file /tst111/ptr/fxdb1251.f, line 25.
(gdb) b 31
Breakpoint 4 at 0x100007cc: file /tst111/ptr/fxdb1251.f, line 31.
(gdb)

After running the program, if I clear all breakpoints and try to set
them again by line number, it works.

Any ideas?

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

iD8DBQFG9dE8qvq7Aov/qQARAnoGAJ9oAM2QSypensiZxsv1fJBvnucUQACfSWFD
zbU+0hlFgADSvx1JGGzkU3E=
=m8M+
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2007-09-23  2:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-15 11:37 Carlos Eduardo Seo
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           ` 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-26 21:51           ` Pierre Muller
2007-09-23  2:52       ` Carlos Eduardo Seo [this message]
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=46F5D13D.2070303@linux.vnet.ibm.com \
    --to=cseo@linux.vnet.ibm.com \
    --cc=brobecker@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).