------- Comment From [email protected] 2015-03-19 12:59 EDT-------
(In reply to comment #14)
> This is interesting, as this is exactly the behavior you get when debugging
> in gdb, and you've made changes in your code, and your breakpoints are now
> out of sync with your code. (because you've added or removed lines) It
> seem like the problem almost certainly has to be that the testsuite has some
> hard-code breakpoints, and these are out of sync with one or more files of
> the actual source code.
Actually this can be seen with this simple testcase (which is not part
of gdb testsuite):
ubuntu@ubuntu:~$ cat array.c
int main (void)
{
int array[1];
return 0;
}
When using gcc-4.9 from community or gcc-4.8 from Ubuntu, 'breakpoint
main' stops at line 5 ('return 0'), which is the expected behavior,
while using the default gcc (4.9) from Ubuntu 15.04, it stops at line 2.
Thus, I can't see how this can be a problem with hard-code breakpoints
from the testsuite.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1420556
Title:
gdb source tests are failing in Ubuntu 15.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1420556/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
