Okay. This occurs when building qt-4.5.3 and only in
3rdparty/webkit/WebCore directory. Because the WebCore.pro file inside
this directory has a CONFIG += no_debug_info in the end.
I am wondering why this CONFIG option was added.
On Thu, Jan 28, 2010 at 10:41 AM, Pankaj Jangid
On 1/26/10 5:08 PM, n179911 wrote:
Thanks. I do have enough disk space.
...
$ git clone git://gitorious.org/webkit/webkit.git WebKit
Initialized empty Git repository in /media/data/WebKit/.git/
remote: Counting objects: 628513, done.
fatal: The remote end hung up unexpectedly
fatal: early EOF
On Wed, Jan 27, 2010 at 6:45 PM, Ariya Hidayat ariya.hida...@gmail.com wrote:
I know that the mail list archives are available, but they are browseable
and not searchable ... other than by whatever Google may pick up.
Using Google is quite helpful, I gave the examples in the first point of
I am using the Qt port of webkit and I am trying to check if a request
is an AJAX request inside of the
FrameLoaderClientQt::dispatchDecidePolicyForNavigationAction(FramePolicyFunction
function, const WebCore::NavigationAction action, const
WebCore::ResourceRequest request,
Ariya Hidayat wrote:
I know that the mail list archives are available, but they are browseable
and not searchable ... other than by whatever Google may pick up.
Using Google is quite helpful, I gave the examples in the first point of
Thanks Ariya,
This is a useful information. My sample application which is using QtWebKit
is crashing in qwebview-setHtml() call so I have created a release build
with debug enabled only inside WebCore.pro. This configuration is working
fine for me to debug my app. The whole Qt withoug -g and
