From: Alvin Beach <abeach@deepvision.ca>
To: gdb@sources.redhat.com
Subject: Re: Program no longer exists [SOLVED - Completely]
Date: Fri, 17 Jun 2005 11:18:00 -0000 [thread overview]
Message-ID: <200506170820.02018.abeach@deepvision.ca> (raw)
In-Reply-To: <200506071546.54443.abeach@deepvision.ca>
On Tuesday 07 June 2005 15:46, Alvin Beach wrote:
> On Monday 06 June 2005 19:29, Alvin Beach wrote:
> > Hello all,
> >
> > I don't know why or how, but after I installed gdb-debuginfo-6.3-14 I can
> > now debug threaded applications.
> >
> > I thought I'd send this out in case someone else has run into the same
> > problem I did.
> >
> > Alvin
>
> Hello all,
>
> I think I know the cause of this problem (Well I got the answer from the
> linux.development.apps newsgroup).
>
> Turns out the glibc and glibc-devel rpms have missed matched versions!
>
> Suse has a security fix for glibc but not glibc-devel. Once I down-graded
> glibc, I was able to debug again.
Just in case someone is experiencing this same problem, SuSE has released a
fix for this. They have patched several rpms, which include:
glibc-i18ndata-2.3.4-23.4
glibc-profile-2.3.4-23.4
glibc-2.3.4-23.4
glibc-locale-2.3.4-23.4
glibc-info-2.3.4-23.4
glibc-devel-2.3.4-23.4
timezone-2.3.4-23.4
So, basically, just do an update and the problem will go away.
--
Please reply to the mailing list.
prev parent reply other threads:[~2005-06-17 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 22:29 Program no longer exists [SOLVED] Alvin Beach
2005-06-06 22:42 ` debugging threaded apps. thread ID missing in corefile Manoj Iyer
2005-06-07 0:09 ` Daniel Jacobowitz
2005-06-07 3:46 ` Eli Zaretskii
2005-06-07 13:10 ` Daniel Jacobowitz
2005-06-12 0:47 ` Mark Kettenis
2005-06-07 0:37 ` Program no longer exists [UNSOLVED] Alvin Beach
2005-06-07 18:45 ` Program no longer exists [SOLVED - 95% sure] Alvin Beach
2005-06-17 11:18 ` Alvin Beach [this message]
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=200506170820.02018.abeach@deepvision.ca \
--to=abeach@deepvision.ca \
--cc=gdb@sources.redhat.com \
/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).