Re: Debugging static library used by a plugin?
Re: Debugging static library used by a plugin?
- Subject: Re: Debugging static library used by a plugin?
- From: Jim Wintermyre <email@hidden>
- Date: Fri, 12 May 2006 16:34:04 -0700
Thanks for the info Eric. After I sent out the original message, it
seemed to randomly start working. In my case, I am testing a single
plugin, and it is the only component linked to the static lib, so it
seems like it should work. Now it appears to work when the first
instance of the plugin is created (usually at least...). For
subsequent instances it doesn't always work, which sounds more like
the issue you were talking about. I'll look into using rbreak for
that.
Thanks,
Jim
At 4:53 PM -0700 5/10/06, Eric Eizenman wrote:
I ran into the same situation when I had a static lib that was being
used by two executables in the same project (for example AudioUnit
process component and AudioUnit view component which are linked
against the same static lib). gdb would stop in the static lib code
only for one of them. The problem as I understood was in the way gdb
reads the debug information. It seems that gdb is assuming that
there is a 1:1 relation between a line of code and executable code.
The way I workaround it was to use rbreak, which will set breakpoint
based on every instance of a given regular expression.
This issue was discussed a few times before, so you could look for
more information in the archives.
------------------------------------------------------------------
Eric Eizenman
BIAS Inc., Audio Software Development
------------------------------------------------------------------
On May 9, 2006, at 5:31 PM, Jim Wintermyre wrote:
I have a sort of complicated debugging scenario that I can't seem
to get working properly. I have a plugin (a Mach-O bundle), which
can be loaded under multiple different host apps (none of which we
have the source to). This plugin links to both a static library,
and a framework, both of which are ours. The plugin project has
subprojects for the static library and the framework. I set up a
custom executable to launch the desired host app, and I can set
breakpoints in the plugin code w/o problems. I also found that if
I open the framework subprojects, I can set breakpoints in those
files as well, and when continuing the debug session from the main
plugin project, it does seem to hit the framework breakpoints as
well.
The problem is with the static library. I can't seem to break in
any source in that project. I tried opening the subproject and
setting breakpoints there, which works for the framework, but that
didn't work here. I tried adding one of the static library source
files directly to the plugin project, and not assigning it to any
target, but that didn't work either.
Any ideas?
Thanks,
Jim
_______________________________________________
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden