Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bmessage breakpoints fail on methods defined in categories #57

Closed
kastiglione opened this issue Dec 2, 2014 · 1 comment · Fixed by #58
Closed

bmessage breakpoints fail on methods defined in categories #57

kastiglione opened this issue Dec 2, 2014 · 1 comment · Fixed by #58

Comments

@kastiglione
Copy link
Contributor

I don't know if there was a recent change or regression to lldb, but in order to set breakpoints on methods defined in categories, the category needs to be included in the breakpoint name.

For example, setting a breakpoint on -setFrame: now has to be:

breakpoint set -n '-[UIView(Geometry) setFrame:]'

Currently, bmessage doesn't consider categories when creating the breakpoint and silently fails on methods defined in categories.

I don't know of anyway to find out the category from the objc runtime. If that's indeed not possible the two ways I fixes I can think of are:

  1. Use a regex breakpoint: br s -r '-\[UIView(\(.+\))? setFrame:\]'
  2. Scrape the category out of the symbol table: target modules dump symtab.

Any better ideas?

@kastiglione kastiglione changed the title bmessage breakpoints fail on methods in defined in categories bmessage breakpoints fail on methods defined in categories Dec 2, 2014
kastiglione added a commit that referenced this issue Dec 4, 2014
KingOfBrian pushed a commit to KingOfBrian/chisel that referenced this issue Dec 19, 2014
@kastiglione
Copy link
Contributor Author

According to my radar, the underlying bug in lldb has been fixed in Xcode 6.3 - Build 6D520o.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant