This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I don't think we should do that. I think we should leave things as they are now, namely, that "break foo" means the function foo in the _current_ module, be that foo.c or bar.c. For the other, the user is required to type "break bar.c:foo".
In C++ and other OO languages, this is different, but in C we shouldn't introduce confusion, IMHO. Someone who debugs a C program doesn't expect to get a breakpoint on a completely different function.
It watches whatever *bar would print, which is one of them. No easy way to get at the other or describe the ambiguity. I wonder once again whether the two-level scheme is really correctly designed; but I have no better ideas.
enjoy, Andrew
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |