[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gdb
Subject:    breakpoint setting weirdness in C++
From:       <allen () webg2 ! com>
Date:       2000-10-17 21:19:02
Message-ID: 14828.49775.685652.131518 () skronk ! webg2 ! com
[Download RAW message or body]


On a RedHat Linux 6.2/Intel system using gcc-2.95.2/gdb-5.0 I am
having the following problems setting breakpoints. 

allen@skronk:~/sandbox/build/adept/adept/tests$ gdb server
GNU gdb 5.0
Copyright 2000 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
(gdb) break log.i:1
No source file named log.i.
(gdb) break log.h:1
No source file named log.h.
(gdb) break log.cpp:1
Breakpoint 1 at 0x8063620: file log.cpp, line 1.
(gdb) break log.i:1
Breakpoint 2 at 0x8064218: file /home/allen/sandbox/build/log/log/log.i, line 1.
(gdb) break log.h:1
Breakpoint 3 at 0x80e18fc: file /home/allen/sandbox/build/log/log/log.h, line 1.
(gdb) quit 
allen@skronk:~/sandbox/build/adept/adept/tests$ 

Two things strike me as weird. The first is that I cannot set a
breakpoint in a *.h or *.i file unless I first set a breakpoint in a
*.cpp file beforehand. The second is that when I set the breakpoint in
the log.cpp file it did not print out the absolution pathname as it
did for the log.h and log.i files. Any clues?

many thanks in advance...

-allen



[prev in list] [next in list] [prev in thread] [next in thread]