Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: DJ Delorie <dj@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: is sim/common documented anywhere?
Date: Fri, 24 Aug 2012 22:10:00 -0000	[thread overview]
Message-ID: <201208241810.45936.vapier@gentoo.org> (raw)
In-Reply-To: <201208242003.q7OK3pEP010608@greed.delorie.com>

[-- Attachment #1: Type: Text/Plain, Size: 910 bytes --]

On Friday 24 August 2012 16:03:51 DJ Delorie wrote:
> Ok, how do I get past this one...
> 
> sim-events.c:1076: assertion failed - events->nr_ticks_to_process != 0
> 
> This happens after sim_create_inferior is called, but before
> sim_engine_run is called.

ah, sometimes i think that error is the bane of my [sim] existence.  
annoyingly, it can arise for a few different reasons.

first, you don't want the common/sim-run.c [1].  although i'll probably just 
gut that already and make it usable since no one ever got back to me and make 
it so it is usable by default ...

second, you're using nrun.c right ?  make sure SIM_RUN_OBJS=nrun.o in your 
Makefile.in.

third, how are you launching ?  `gdb` or `run` ?

fourth, i vaguely recall not fulling initializing the state in the arch 
sim_open() can cause this to trip.
-mike

1: http://sourceware.org/ml/gdb/2010-02/msg00046.html

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-08-24 22:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 22:58 DJ Delorie
2012-08-22 23:23 ` Mike Frysinger
2012-08-22 23:42   ` DJ Delorie
2012-08-23  1:12     ` Mike Frysinger
2012-08-24 20:04       ` DJ Delorie
2012-08-24 22:10         ` Mike Frysinger [this message]
2012-08-25  0:50           ` DJ Delorie
2012-08-25  5:32             ` Mike Frysinger

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=201208241810.45936.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=dj@redhat.com \
    --cc=gdb@sourceware.org \
    /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