From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: libibverbs and versions
Date: Wed, 02 Jun 2010 09:46:39 -0700 [thread overview]
Message-ID: <adaeigptma8.fsf@roland-alpha.cisco.com> (raw)
In-Reply-To: <4C067DE0.8020508-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org> (Steve Wise's message of "Wed, 02 Jun 2010 10:50:56 -0500")
> I have this library I'm writing that uses libibverbs. Somehow it
> seems to be using the 1.0 version instead of the newer version (I'm
> guessing). When I call ibv_create_cq() I get a seg fault and the
> stack looks like this:
>
> #0 0x000000319d80871d in pthread_mutex_lock () from /lib64/libpthread.so.0
> #1 0x00007f60e93fac9a in __ibv_create_cq (context=0x7f60e8597c51, cqe=256,
> cq_context=0x0, channel=0x0, comp_vector=0) at src/verbs.c:278
> #2 0x00007f60e93f727f in __ibv_create_cq_1_0 (context=0x61db30, cqe=256,
> cq_context=0x0, channel=0x0, comp_vector=0) at src/compat-1_0.c:649
Code compiled against libibverbs 1.1 shouldn't ever hit the 1.0
compatibility code. libibverbs is using versioned symbols, so if your
library is built/linked correctly, it should pick up the 1.1 versions.
How are you building your library?
- R.
--
Roland Dreier <rolandd-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org> || For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-02 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 15:50 libibverbs and versions Steve Wise
[not found] ` <4C067DE0.8020508-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-06-02 16:46 ` Roland Dreier [this message]
[not found] ` <adaeigptma8.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-06-02 17:39 ` Steve Wise
2010-06-02 17:32 ` Jason Gunthorpe
[not found] ` <20100602173245.GG15969-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-06-02 17:40 ` Steve Wise
[not found] ` <4C069774.4050402-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-06-02 17:59 ` Jason Gunthorpe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=adaeigptma8.fsf@roland-alpha.cisco.com \
--to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox