Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Torsten Mohr <tmohr@s.netic.de>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: V850E simulator, assembler single-step never returns?!?
Date: Mon, 05 Jun 2006 22:36:00 -0000	[thread overview]
Message-ID: <200606060036.09212.tmohr@s.netic.de> (raw)
In-Reply-To: <448497BC.5020907@redhat.com>

Hi,

i just single-stepped in the console (si).  It shows the same result
plus:
The last line in the console i see is:
[not visible]../../../../newlib-1.14.0/newlib/libc/stdlib/mlock.c:51
I attached the part from mlock.c below with line 51 marked.
Though i don't think it can be related to that, as in the assembler
this line just results to "jmp [lp]", also when i look at it in
gdb console with "l *0x11f4".

I made a screenshot of the whole thing (128k).  Is it of any help if i
send it to anybody?

Please note that i'm not sure if code generation for the target
is perfect.  But i'm sure that i did not apply any changes to
insight.  I configured in a bash script:

function do_gdb ( ) {
    mkdir -p gdb
    cd gdb
    rm -rf *
    ../../insight-6.4/configure \
    --target=v850-unknown-elf \
    --prefix=/opt/v850e \
    --with-newlib \
    --enable-sim \
    --disable-nls
#    make all-sim
#    make install    
    cd ..
}

regarding the combination of "make" i'm not really sure, i only
compiled and installed the simulator.

I directly posted to the gdb list because i think this is
related to the underlying gdb/simulator.

Would it be of any help if i supply the ELF file to anybody?


Best regards,
Torsten.

FILE mlock.c
void
__malloc_lock (ptr)
     struct _reent *ptr;
{
#ifndef __SINGLE_THREAD__
  __lock_acquire_recursive (__malloc_lock_object); // line 51
#endif
}



> Daniel Jacobowitz wrote:
> > Have you considered reporting problems with Insight to the Insight
> > list?
>
> Better yet, try opening a console and stepping manually (or use
> v850-elf-gdb). At least then you'll know that it is or is not a problem
> with insight vs gdb.
>
> Keith


  parent reply	other threads:[~2006-06-05 22:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-05 19:42 Torsten Mohr
2006-06-05 20:42 ` Daniel Jacobowitz
2006-06-05 20:44   ` Keith Seitz
2006-06-05 20:50     ` Daniel Jacobowitz
2006-06-05 21:02       ` Keith Seitz
2006-06-05 22:36     ` Torsten Mohr [this message]
2006-06-05 22:41       ` Daniel Jacobowitz
2006-06-06  9:46         ` Torsten Mohr
2006-06-07 23:24           ` Torsten Mohr
2006-06-08  1:22             ` Daniel Jacobowitz
2006-06-08 12:12               ` Torsten Mohr
2006-06-08 21:37               ` Torsten Mohr
2006-06-05 20:34 Torsten Mohr

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=200606060036.09212.tmohr@s.netic.de \
    --to=tmohr@s.netic.de \
    --cc=gdb@sourceware.org \
    --cc=keiths@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