public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/794] New: Segfault with LD_DEBUG=ALL
@ 2005-03-17 14:32 paul at codesourcery dot com
  2005-03-17 14:35 ` [Bug libc/794] " paul at codesourcery dot com
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: paul at codesourcery dot com @ 2005-03-17 14:32 UTC (permalink / raw)
  To: glibc-bugs

I'm getting a segfault when setting LD_DEBUG=all
The segfault occurs because we end up doing something equivalent to 
_dl_debug_printf("%s", NULL);

I't quite possible that this is a bug elsewhere, but given this routine is
specifically for debugging purposes it sems sensible to make it robust to
unusual input.

-- 
           Summary: Segfault with LD_DEBUG=ALL
           Product: glibc
           Version: 2.3.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: paul at codesourcery dot com
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: arm-none-linux-gnueabi


http://sources.redhat.com/bugzilla/show_bug.cgi?id=794

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libc/794] Segfault with LD_DEBUG=ALL
  2005-03-17 14:32 [Bug libc/794] New: Segfault with LD_DEBUG=ALL paul at codesourcery dot com
@ 2005-03-17 14:35 ` paul at codesourcery dot com
  2005-03-17 21:09 ` roland at gnu dot org
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: paul at codesourcery dot com @ 2005-03-17 14:35 UTC (permalink / raw)
  To: glibc-bugs


------- Additional Comments From paul at codesourcery dot com  2005-03-17 14:34 -------
Created an attachment (id=438)
 --> (http://sources.redhat.com/bugzilla/attachment.cgi?id=438&action=view)
Patch to fix bug

Fixes bug by printing "(null)" as appropriate, like normal printf does.

-- 


http://sources.redhat.com/bugzilla/show_bug.cgi?id=794

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libc/794] Segfault with LD_DEBUG=ALL
  2005-03-17 14:32 [Bug libc/794] New: Segfault with LD_DEBUG=ALL paul at codesourcery dot com
  2005-03-17 14:35 ` [Bug libc/794] " paul at codesourcery dot com
@ 2005-03-17 21:09 ` roland at gnu dot org
  2005-03-18  3:40 ` paul at codesourcery dot com
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: roland at gnu dot org @ 2005-03-17 21:09 UTC (permalink / raw)
  To: glibc-bugs


------- Additional Comments From roland at gnu dot org  2005-03-17 21:09 -------
This report lacks a test case.  If this is an arm-specific problem, please
figure out whether it happens only in some arm-specific code.  

Note that Target is a meaningless field for libc.
If you want to indicate the platform of interest, that's Host.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING


http://sources.redhat.com/bugzilla/show_bug.cgi?id=794

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libc/794] Segfault with LD_DEBUG=ALL
  2005-03-17 14:32 [Bug libc/794] New: Segfault with LD_DEBUG=ALL paul at codesourcery dot com
  2005-03-17 14:35 ` [Bug libc/794] " paul at codesourcery dot com
  2005-03-17 21:09 ` roland at gnu dot org
@ 2005-03-18  3:40 ` paul at codesourcery dot com
  2005-03-20  2:06 ` gotom at debian dot or dot jp
  2005-03-20  6:39 ` roland at gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: paul at codesourcery dot com @ 2005-03-18  3:40 UTC (permalink / raw)
  To: glibc-bugs


------- Additional Comments From paul at codesourcery dot com  2005-03-18 03:40 -------
This happened with an internal modified version of glibc, and only      
occurred because another bit of glibc was broken.   
   
However tracking down that bug would probably have been easier if     
_dl_debug_printf didn't segfault.  Tracking back a fault is much easier when 
you can see the debug output going wrong, rather than trying to deal with 
segfaults on a target without a working gdb. 
   
The issue is not specific to a particular target. 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
  GCC build triplet|i686-pc-linux-gnu           |
   GCC host triplet|i686-pc-linux-gnu           |
 GCC target triplet|arm-none-linux-gnueabi      |


http://sources.redhat.com/bugzilla/show_bug.cgi?id=794

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libc/794] Segfault with LD_DEBUG=ALL
  2005-03-17 14:32 [Bug libc/794] New: Segfault with LD_DEBUG=ALL paul at codesourcery dot com
                   ` (2 preceding siblings ...)
  2005-03-18  3:40 ` paul at codesourcery dot com
@ 2005-03-20  2:06 ` gotom at debian dot or dot jp
  2005-03-20  6:39 ` roland at gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: gotom at debian dot or dot jp @ 2005-03-20  2:06 UTC (permalink / raw)
  To: glibc-bugs


------- Additional Comments From gotom at debian dot or dot jp  2005-03-20 02:06 -------
In most case, passing NULL to _dl_debug_printf("%s") is glibc's bug.
It's small improvement for such a special case.  Committers,
please judge to put it or not.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|gotom at debian dot or dot  |roland at gnu dot org
                   |jp                          |
             Status|NEW                         |ASSIGNED


http://sources.redhat.com/bugzilla/show_bug.cgi?id=794

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libc/794] Segfault with LD_DEBUG=ALL
  2005-03-17 14:32 [Bug libc/794] New: Segfault with LD_DEBUG=ALL paul at codesourcery dot com
                   ` (3 preceding siblings ...)
  2005-03-20  2:06 ` gotom at debian dot or dot jp
@ 2005-03-20  6:39 ` roland at gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: roland at gnu dot org @ 2005-03-20  6:39 UTC (permalink / raw)
  To: glibc-bugs


------- Additional Comments From roland at gnu dot org  2005-03-20 06:39 -------
I don't think it's warranted.  It seems as likely to mask a bug as to make
debugging easier.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |WONTFIX


http://sources.redhat.com/bugzilla/show_bug.cgi?id=794

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2005-03-20  6:39 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-03-17 14:32 [Bug libc/794] New: Segfault with LD_DEBUG=ALL paul at codesourcery dot com
2005-03-17 14:35 ` [Bug libc/794] " paul at codesourcery dot com
2005-03-17 21:09 ` roland at gnu dot org
2005-03-18  3:40 ` paul at codesourcery dot com
2005-03-20  2:06 ` gotom at debian dot or dot jp
2005-03-20  6:39 ` roland at gnu dot org

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).