[webkit-dev] Made a debug build of WebKit.Framework. GDB ignores breakpoints?

[Eddy Bruël]

Hi guys,

I recently found a potential bug in WebKit:
<https://bugs.webkit.org/show_bug.cgi?id=31607>
https://bugs.webkit.org/show_bug.cgi?id=31607

It's fairly crucial for me that this feature should work as advocated (or
that there is at least
a possible workaround for it), so I thought I'd take a shot a finding the
bug myself.

I've checked out the most recent WebKit sources, and made a debug build. I
then linked my
program against the resulting WebKit.Framework, and used the headers in the
corresponding
WebKit.Framework/Headers directory. I can now set breakpoints in my own
code, and then
do a stack trace to see which WebKit source file I came from.

Problem is, next I tried setting breakpoints in these source files,
but these seem to be
completely ignored by GDB altogether. It stops execution just fine on the
breakpoints in my
own source file, just not on those in the WebKit source files (even though
these functions are
part of the stack trace, and are therefore definitely being called).

Without any way of setting breakpoints in the WebKit source code I have no
realistic hope of
ever finding the problem myself, so I hope you guys can help me out here. Is
there anything
obvious that I'm doing wrong here? I'm fairly new at debugging external
libraries, so maybe I
am overlooking something.

Cheers,


Eddy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20091118/d5185642/attachment.html>