From: "Lev Assinovsky" <LAssinovsky@algorithm.aelita.com>
To: "Daniel Jacobowitz" <drow@mvista.com>
Cc: <gdb@sources.redhat.com>, "Kevin Buettner" <kevinb@redhat.com>
Subject: RE: gdb 5.3 bug
Date: Fri, 07 Mar 2003 14:35:00 -0000 [thread overview]
Message-ID: <3F6F4712B759A34ABD453A8B39C10D6233128D@bagman.edm.com> (raw)
Thanks. Also
thank you and Kevin very much.
The fix is a really great event in our
team.
----
Lev Assinovsky
Aelita Software Corporation
O&S Core Division, Programmer
ICQ# 165072909
> -----Original Message-----
> From: Daniel Jacobowitz [mailto:drow@mvista.com]
> Sent: Friday, March 07, 2003 5:27 PM
> To: Lev Assinovsky
> Cc: gdb@sources.redhat.com; Kevin Buettner
> Subject: Re: gdb 5.3 bug
>
>
> On Fri, Mar 07, 2003 at 02:05:22PM +0300, Lev Assinovsky wrote:
> > I can's say that the bug fixed
> > but I found how to work around!!!
> > The problem was that gnu "ld" put "/usr/lib/libc.so.1" in place
> > of interpreter in executable.
> > If to use gcc option -Xlinker "--dynamic-linker" -Xlinker
> /usr/lib/ld.so.1
> > gdb works fine!
>
> Well, since current versons of the GNU tools won't do this, I think
> we're done. Great!
>
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
>
next reply other threads:[~2003-03-07 14:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 14:35 Lev Assinovsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-07 11:05 Lev Assinovsky
2003-03-07 14:26 ` Daniel Jacobowitz
2003-03-05 17:32 Lev Assinovsky
2003-03-05 17:52 ` Kevin Buettner
2003-03-05 17:12 Lev Assinovsky
2003-03-05 17:23 ` Daniel Jacobowitz
2003-03-05 16:54 Lev Assinovsky
2003-03-05 16:06 Lev Assinovsky
2003-03-05 16:12 ` Daniel Jacobowitz
2003-03-05 14:27 Lev Assinovsky
2003-03-05 15:57 ` Daniel Jacobowitz
2003-03-01 17:40 Lev Assinovsky
2003-03-01 16:13 Lev Assinovsky
2003-03-01 15:59 Lev Assinovsky
2003-03-01 16:05 ` Daniel Jacobowitz
2003-02-27 18:11 Lev Assinovsky
2003-02-27 19:09 ` Daniel Jacobowitz
2003-02-28 17:18 ` Daniel Jacobowitz
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=3F6F4712B759A34ABD453A8B39C10D6233128D@bagman.edm.com \
--to=lassinovsky@algorithm.aelita.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@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