public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/15271] dlmopen()ed shared library with LM_ID_NEWLM crashes if it fails dlsym() twice
Date: Wed, 27 Mar 2013 04:03:00 -0000	[thread overview]
Message-ID: <bug-15271-131-715BEY55Al@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15271-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15271

--- Comment #5 from Carlos O'Donell <carlos at redhat dot com> 2013-03-27 04:03:21 UTC ---
(In reply to comment #4)
> Hi Carlos,
> 
> My employer doesn't currently have the necessary paperwork in place to assign
> copyright to the FSF (and getting that paperwork in place is unlikely to happen
> in the near future).  I'm happy to help as long as my contributions can be
> categorized as an idea and not require explicit assignment of copyright.  Is
> that possible for testsuite updates?
> 
> If this patch is accepted, I would like to have it back-ported to Debian glibc.
> I'm not aware of any other maintenance branches where this would be needed at
> this time.

Thanks for setting the expectation. In general you would need copyright
assignment to do any further work. We can take it from here, but it might not
happen as quickly as you wish :-(

Thanks for posting the patch and bug report though. We do appreciate it.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2013-03-27  4:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 17:23 [Bug dynamic-link/15271] New: " brnguyen at nvidia dot com
2013-03-12 20:23 ` [Bug dynamic-link/15271] " carlos at redhat dot com
2013-03-14 23:24 ` brnguyen at nvidia dot com
2013-03-17 17:25 ` carlos at redhat dot com
2013-03-21  0:46 ` brnguyen at nvidia dot com
2013-03-27  4:03 ` carlos at redhat dot com [this message]
2013-10-02 22:25 ` neleai at seznam dot cz
2014-06-13 18:42 ` fweimer at redhat dot com
2020-07-23 19:12 ` ajax at redhat dot com
2020-07-23 21:00 ` fweimer at redhat dot com
2020-07-23 21:05 ` fweimer at redhat dot com
2021-04-21 19:42 ` fweimer at redhat dot com
2021-06-09 13:57 ` fweimer at redhat dot com
2021-06-09 15:17 ` fweimer at redhat dot com

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=bug-15271-131-715BEY55Al@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).