Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#24364 - [glibc]

Attached to Project: Arch Linux
Opened by Screen Silently (ScreenSilently) - Saturday, 21 May 2011, 00:17 GMT
Last edited by Allan McRae (Allan) - Saturday, 21 May 2011, 02:15 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Hello,

/lib/libc-2.13.so causes segmentation errors that in other distros DO NOT happen, using several binarys in several different computers..

More specifically using the gdb debugging tool I'm getting:
Program terminated with signal 11, Segmentation fault.
#0 0xb75e0495 in fwrite () from /lib/libc.so.6

// or //
Program terminated with signal 11, Segmentation fault.
#0 0xb7684b9d in __uflow () from /lib/libc.so.6

So, something must be definitely wrong with the way you compiled the library.
Please check this out.

Thank you!
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 21 May 2011, 02:15 GMT
Reason for closing:  Works for me
Additional comments about closing:  See final comment
Comment by Screen Silently (ScreenSilently) - Saturday, 21 May 2011, 01:08 GMT
This is from the error log:
May 21 00:30:06 desktopc kernel: [40371.575119] samuzk.[8894]: segfault at 14 ip b766ab9d sp bffda508 error 4 in libc-2.13.so[b75ff000+15f000]
Comment by Allan McRae (Allan) - Saturday, 21 May 2011, 02:14 GMT
The is absolutely no information provided here for anyone to track down this issue. Create a new bug report with some actual details one how to replicate.

Loading...