Mario, “-n” is trying to do things like
(lldb) break set -n foo will break on bar::foo, etc… So it tries to parse up the name, and weird names like this can trip it up. Greg recently fixed some bugs with the -n parsing for ObjC names which might have caused it to break on your names. Does breakpoint setting work when you use “break set -F <NAME>” for these sorts of names. This option does an exact match against the symbol name and doesn’t try to be smart about it, it’s there as a fallback for odd names lldb fails to parse up correctly. Jim > On Nov 5, 2014, at 1:06 AM, Mario Zechner <badlogicga...@gmail.com> wrote: > > Hi, > > we are using SBTarget::BreakpointCreateByName so set breakpoint on symbol > names. This works as long as no special characters are in the symbol name. > Our name mangling can produce symbols like: > > [J]com.robovm.debug.server.apps.SleepLoop.startingUp()V > > for which SBTarget::BreakpointCreateByName fails to resolve locations. > > This happens with the latest trunk version of LLDB, it worked with a snapshot > from the 29th of September. > > We currently work around this issue by using > SBTarget::BreakpointCreateByRegex. > > Thanks, > Mario > _______________________________________________ > lldb-dev mailing list > lldb-dev@cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev _______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
