Bug 14951 - Once set point appears again in the new session
Summary: Once set point appears again in the new session
Status: RESOLVED INVALID
Alias: None
Product: gdb
Classification: Unclassified
Component: breakpoints (show other bugs)
Version: 7.5
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-13 02:32 UTC by George Galeev
Modified: 2013-04-17 20:27 UTC (History)
1 user (show)

See Also:
Host: x86_64-pc-linux-gnu
Target: x86_64-pc-linux-gnu
Build: x86_64-pc-linux-gnu
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description George Galeev 2012-12-13 02:32:47 UTC
I'm not sure that this is a bug, but please explain the following behavior. I add a point anywhere and phantom point (added earlier, in another session) hit, and in each new session. And the hit point have a wrong name.Phantom point remains even after a reboot. I do not know how there appears such a point, but I know that it is present in the system now. Slightly more detailed description of the behavior is on the CodeBlocks forum, where I came from (http://forums.codeblocks.org/index.php/topic,1823.msg118089.html#msg118089).
Please check first with the log below.

I add a point for the line 47, but hit phantom point at 146. Point at 146 hit always and does not depend on the number of line in which I add a my real point.

HSLab Linux64_Debug # /usr/bin/gdb -nx -fullname  -args /main/rain/dev/RAIN/Platforms/Linux64_Debug/ClientLauncher
GNU gdb (Gentoo 7.5 p1) 7.5
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /main/rain/dev/RAIN/Platforms/Linux64_Debug/ClientLauncher...done.
(gdb) break "/main/rain/dev/src/include/RainCore/Containers/DynamicArray.hpp:47"
No source file named /main/rain/dev/src/include/RainCore/Containers/DynamicArray.hpp.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 ("/main/rain/dev/src/include/RainCore/Containers/DynamicArray.hpp:47") pending.
(gdb) run
Starting program: /main/rain/dev/RAIN/Platforms/Linux64_Debug/ClientLauncher 
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

2012.12.13 06:05:02.468173 : Запуск ядра
2012.12.13 06:05:02.470649 : Multithread mode: 8/8/8[New Thread 0x7ffff6d61700 (LWP 6532)]
[New Thread 0x7fffeffff700 (LWP 6533)]
[New Thread 0x7ffff645f700 (LWP 6534)]
[New Thread 0x7ffff5c5e700 (LWP 6535)]
[New Thread 0x7ffff545d700 (LWP 6536)]
[New Thread 0x7ffff4c5c700 (LWP 6537)]
[New Thread 0x7fffef7fe700 (LWP 6538)]

2012.12.13 06:05:02.473839 : Launched MasterCore
2012.12.13 06:05:02.475385 : Intercore initialization complete
2012.12.13 06:05:02.540758 : ++ClientGate
2012.12.13 06:05:02.571394 : ++AccountsDatabase
2012.12.13 06:05:02.712264 : ++WorldsServer
2012.12.13 06:05:03.441712 : ++Client[Switching to Thread 0x7ffff4c5c700 (LWP 6537)]

Breakpoint 1, Rain::DynamicArrayImplStack<Rain::Handler*, Rain::DynamicArrayDefaultBufferStrategy>::end (this=0x7ffff7764fc8) at ../include/RainCore/Containers/DynamicArray.hpp:146
▒▒/main/rain/dev/src/include/RainCore/Containers/DynamicArray.hpp:146:6204:beg:0x7ffff7d2a5ba
(gdb) info breakpoints
Num     Type           Disp Enb Address            What
1       breakpoint     keep y   0x00007ffff7d2a5ba in Rain::DynamicArrayImplStack<Rain::Handler*, Rain::DynamicArrayDefaultBufferStrategy>::end() at ../include/RainCore/Containers/DynamicArray.hpp:47
        breakpoint already hit 1 time
Comment 1 George Galeev 2012-12-13 06:15:09 UTC
Real breakpoints also hit, so it turns out that I have "n + 1" breakpoints.
Comment 2 George Galeev 2013-04-17 20:27:29 UTC
Error message: "No source file named".
Solved by setting correct paths to search source files.