Bug 235144 - *** glibc detected *** xchat-gnome: free(): invalid pointer on start up
*** glibc detected *** xchat-gnome: free(): invalid pointer on start up
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: xchat-gnome (Show other bugs)
rawhide
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Brian Pepple
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-03 19:05 EDT by David Nielsen
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version: 0.17-3
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-04-03 21:06:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
terminal output (13.47 KB, text/plain)
2007-04-03 19:05 EDT, David Nielsen
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Desktop 426066 None None None Never

  None (edit)
Description David Nielsen 2007-04-03 19:05:44 EDT
Description of problem:
I'm getting the attached output on every start up of xchat-gnome

Version-Release number of selected component (if applicable):
xchat-gnome-0.17-2.fc7
libsexy-0.1.11-1.fc7
gtk2-2.10.11-3.fc7
glibc-2.5.90-20
glib2-2.12.11-1.fc7

How reproducible:
100%

Steps to Reproduce:
1. Start xchat-gnome
  
Actual results:
Notice backtrace

Expected results:
xchat-gnome started correctly

Additional info:
Comment 1 David Nielsen 2007-04-03 19:05:44 EDT
Created attachment 151631 [details]
terminal output
Comment 2 Brian Pepple 2007-04-03 19:56:43 EDT
Hmmm, odd. I haven't had any issues with 0.17, though I don't have a x86_64
machine. I'll try to give this a look tomorrow, and I've also opened a bug upstream.
Comment 3 Brian Pepple 2007-04-03 21:06:15 EDT
Should be fixed in xchat-gnome-0.17-3, which should go out in the next package
signing.  If that doesn't fix it for you, please re-open this bug. Thanks.

Note You need to log in before you can comment on or make changes to this bug.