Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: arkkimede <arkkimede@gmail.com>
To: lidar <lidar@trego.co.il>
Cc: gdb@gcc.gnu.org
Subject: Re: not able to debug threads - gcc configuration problem?
Date: Mon, 08 Jun 2009 13:47:00 -0000	[thread overview]
Message-ID: <e720e020906080646w483ac035w2ead9287c85e3b6@mail.gmail.com> (raw)
In-Reply-To: <4A2D05B5.4040304@trego.co.il>

For your information, I can't debug in cygwin a mixed code with c and
assembly using like assembler nasm.
In linux (debian) yes.
Someone advice me to update cygwin I download last release of cygwin
but i doesn't work.
I'm non able to see the assembler code into the debugger
BR

On Mon, Jun 8, 2009 at 2:36 PM, lidar<lidar@trego.co.il> wrote:
> Hello,
>
> I have been attempting to compile a cross-toolchain, to use over Cygwin, for
> a PowerPC target.
>
> So far i have been able to compile and run a multi-threaded program on
> board.
>
> The trouble is, i haven't been able to debug threads with GDB:
>
> 1. when i dont set breakpoints in the thread - the gdb breaks on
> _pthread_sigsuspend upon the pthread_create call, and the program continues
> to completion
> when i say "c".
>
> 2. when i set a breakpoint in the thread, upon pthread_create the program
> exits (with exit value 0), and the gdb reports "program exited normally".
>
>
> Luckily, i do have a fine installation of montavista, so i did a little
> test: i compiled the same basic program on the montavista, ran it on the
> board
> and attempted debugging it with my cygwin gdb. THIS ONE WORKED!  my gdb
> reported threads and agreed to break upon thread breakpoints.
>
> does this mean my gdb is fine?
>
> i also took my Cygwin-compiled program, ran it on the board and tried
> debugging it from the montavista gdb - this one failed in pretty much the
> same way
> i described above.
>
>
> i suspect either my toolchain configuration is bad, or my Cygwin
> installation is missing something.
>
> the toolchain configuration i used is:
>
> TARGET=powerpc-603e-linux-gnu
> TARGET_CFLAGS="-O -mcpu=603e"
> GCC_EXTRA_CONFIG="--with-cpu=603e --enable-cxx-flags=-mcpu=603e"
>
> BINUTILS_DIR=binutils-2.16.1
> GCC_CORE_DIR=gcc-3.3.6
> GCC_DIR=gcc-4.1.0
> GLIBC_DIR=glibc-2.3.6
> LINUX_DIR=linux-2.6.15.4
> LINUX_SANITIZED_HEADER_DIR=linux-libc-headers-2.6.12.0
> GLIBCTHREADS_FILENAME=glibc-linuxthreads-2.3.6
> GDB_DIR=gdb-6.5
>
>
> any ideas or help would be much appreciated.
>
> Lidar
>
>


      reply	other threads:[~2009-06-08 13:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08 12:36 lidar
2009-06-08 13:47 ` arkkimede [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=e720e020906080646w483ac035w2ead9287c85e3b6@mail.gmail.com \
    --to=arkkimede@gmail.com \
    --cc=gdb@gcc.gnu.org \
    --cc=lidar@trego.co.il \
    /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