From: "Eric Bénard" <eric@eukrea.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Jansa <martin.jansa@gmail.com>,
Martin, Patches,
about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] Revert "gdb-cross-canadian: build gdb with python support"
Date: Thu, 22 Mar 2012 14:14:55 +0100 [thread overview]
Message-ID: <20120322141455.644058f0@eb-e6520> (raw)
In-Reply-To: <CAMKF1srORF53h-V+fKTjJn2jWg=f6nOaMf_eUmYPLnW-ovc7NQ@mail.gmail.com>
Le Thu, 22 Mar 2012 05:57:46 -0700,
Khem Raj <raj.khem@gmail.com> a écrit :
> On Thu, Mar 22, 2012 at 5:43 AM, Eric Bénard <eric@eukrea.com> wrote:
> > you are right :
> >
> > $ sudo rm ../../lib/python2.7/lib-dynload/readline.so
>
> ok another experiment instead of deleting readline.so make a copy of
> it and call it
> readline_d.so in the same dir or whereever gdb looks for debug symbols
> and see if it still works or do you get the segfault again.
true :
[ebenard@eb-e6520 lib-dynload]$ sudo mv readline.so readline_d.so
[ebenard@eb-e6520 lib-dynload]$ arm-oe-linux-gnueabi-gdb
GNU gdb (GDB) 7.4
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html> This is free software: you are free
to change and redistribute it. There is NO WARRANTY, to the extent
permitted by law. Type "show copying" and "show warranty" for details.
This GDB was configured as "--host=x86_64-oesdk-linux
--target=arm-oe-linux-gnueabi". For bug reporting instructions, please
see: <http://www.gnu.org/software/gdb/bugs/>.
(gdb) quit
Eric
next prev parent reply other threads:[~2012-03-22 13:23 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 16:35 [PATCH 0/1] fix for the sdk gdb issue nitin.a.kamble
2012-03-21 16:35 ` [PATCH 1/1] Revert "gdb-cross-canadian: build gdb with python support" nitin.a.kamble
2012-03-21 17:07 ` Eric Bénard
2012-03-21 17:47 ` Kamble, Nitin A
2012-03-21 17:52 ` Eric Bénard
2012-03-21 17:57 ` Kamble, Nitin A
2012-03-21 18:02 ` Eric Bénard
2012-03-21 18:07 ` Kamble, Nitin A
2012-03-21 19:32 ` Eric Bénard
2012-03-21 19:49 ` Martin Jansa
2012-03-21 20:48 ` Kamble, Nitin A
2012-03-21 21:02 ` Eric Bénard
2012-03-21 21:12 ` Kamble, Nitin A
2012-03-21 21:35 ` Eric Bénard
2012-03-21 21:53 ` Kamble, Nitin A
2012-03-21 22:05 ` Eric Bénard
2012-03-21 22:10 ` Kamble, Nitin A
2012-03-21 22:21 ` Saul Wold
2012-03-21 22:37 ` Eric Bénard
2012-03-21 22:55 ` Kamble, Nitin A
2012-03-21 23:07 ` Kamble, Nitin A
2012-03-22 12:09 ` Eric Bénard
2012-03-21 22:22 ` Kamble, Nitin A
2012-03-22 8:47 ` Martin Jansa
2012-03-22 8:50 ` Eric Bénard
2012-03-22 0:27 ` Khem Raj
2012-03-22 1:58 ` Kamble, Nitin A
2012-03-22 4:24 ` Khem Raj
2012-03-22 4:55 ` Kamble, Nitin A
2012-03-22 5:06 ` Khem Raj
2012-03-22 5:42 ` Khem Raj
2012-03-22 12:13 ` Eric Bénard
2012-03-22 12:17 ` Khem Raj
2012-03-22 12:43 ` Eric Bénard
2012-03-22 12:57 ` Khem Raj
2012-03-22 13:14 ` Eric Bénard [this message]
2012-03-22 13:34 ` Eric Bénard
2012-03-22 13:54 ` Khem Raj
2012-03-22 16:20 ` Kamble, Nitin A
2012-03-22 16:38 ` Khem Raj
2012-03-22 17:38 ` Kamble, Nitin A
2012-03-22 19:16 ` Khem Raj
2012-03-22 21:31 ` Eric Bénard
2012-03-22 21:40 ` Kamble, Nitin A
2012-03-23 8:07 ` Eric Bénard
2012-03-22 21:48 ` Kamble, Nitin A
2012-03-23 5:33 ` Khem Raj
2012-03-23 6:29 ` Khem Raj
2012-03-23 7:12 ` Khem Raj
2012-03-23 8:31 ` Eric Bénard
2012-03-23 12:07 ` Khem Raj
2012-03-23 16:07 ` Kamble, Nitin A
2012-03-21 22:04 ` Kamble, Nitin A
2012-03-21 22:09 ` Eric Bénard
2012-03-21 23:25 ` Kamble, Nitin A
2012-03-21 23:29 ` Richard Purdie
2012-03-21 21:48 ` Kamble, Nitin A
2012-03-21 19:04 ` Kamble, Nitin A
2012-03-21 19:36 ` Eric Bénard
2012-03-21 19:48 ` Kamble, Nitin A
2012-03-21 17:58 ` Martin Jansa
-- strict thread matches above, loose matches on Subject: below --
2012-03-23 16:36 Khem Raj
2012-03-23 17:01 ` Kamble, Nitin A
2012-03-23 17:44 ` Richard Purdie
2012-03-23 18:01 ` Khem Raj
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=20120322141455.644058f0@eb-e6520 \
--to=eric@eukrea.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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