Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
Re: Where is curlx_dyn_addn defined?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Rainer Canavan via curl-library <curl-library_at_lists.haxx.se>
Date: Fri, 31 May 2024 13:42:45 +0200
On Wed, May 29, 2024 at 7:39 PM Bill Pierce via curl-library
<curl-library_at_lists.haxx.se> wrote:
> Daniel, I don't want to build libcurl, at least not at the moment. I want to use the functions in libcurl by incorporating their source files into my little test program, sort of like the curl tool does. That way I can put in breakpoints, single-step and look at variables to see how it all works.
If you're usually using a curl library from a package supplied by one
of the common linux distributions, don't do that. Just install the
debug info packages for libcurl and any of its dependencies. Your
debugger should pick them up automatically. For fedora or RHEL,
there's https://dnf-plugins-core.readthedocs.io/en/latest/debuginfo-install.html.
For Debian/Ubuntu you can install the debug info packages one by one
(you'll probably have to use ldd and dpkg -S to determine which ones
you need) or you can just have gdb download them from the internet,
see https://wiki.debian.org/HowToGetABacktrace. I should hope that
solutions exist to achieve the same in Windows, macos or wherever
you're getting your curl library from. In the worst case, find out how
that library was built, and re-build the package after adding the
necessary flags to include debug info.
rainer
Date: Fri, 31 May 2024 13:42:45 +0200
On Wed, May 29, 2024 at 7:39 PM Bill Pierce via curl-library
<curl-library_at_lists.haxx.se> wrote:
> Daniel, I don't want to build libcurl, at least not at the moment. I want to use the functions in libcurl by incorporating their source files into my little test program, sort of like the curl tool does. That way I can put in breakpoints, single-step and look at variables to see how it all works.
If you're usually using a curl library from a package supplied by one
of the common linux distributions, don't do that. Just install the
debug info packages for libcurl and any of its dependencies. Your
debugger should pick them up automatically. For fedora or RHEL,
there's https://dnf-plugins-core.readthedocs.io/en/latest/debuginfo-install.html.
For Debian/Ubuntu you can install the debug info packages one by one
(you'll probably have to use ldd and dpkg -S to determine which ones
you need) or you can just have gdb download them from the internet,
see https://wiki.debian.org/HowToGetABacktrace. I should hope that
solutions exist to achieve the same in Windows, macos or wherever
you're getting your curl library from. In the worst case, find out how
that library was built, and re-build the package after adding the
necessary flags to include debug info.
rainer
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2024-05-31