Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Squal <pmarty@enssat.fr>
To: gdb@sources.redhat.com
Subject: remote debugging with m68k-stub
Date: Wed, 14 Aug 2002 02:34:00 -0000	[thread overview]
Message-ID: <3D5A2543.79DAA828@enssat.fr> (raw)

I'm trying to debug some program with the help of 
the m68k stub file. 
When I start the program in the remote target 
(motorola 68000) the connexion with gdb 
(in the host machine Sparc Sun Solaris) seems 
to be a succes:
	
	(gdb) target remote mark:5000
	Remote debugging using mark:5000
	0x00840007 in ?? ()
	(gdb) bt
	#0  0x00381118 in ?? ()
	#1  0x00010156 in ?? ()
	(gdb)

PS: 0x00840007 and 0x00381118 not corresponding
    to a correct memory acces.
A lot of data packet is send throw the serial link.


After that, I try to continue the program execution
with the continue gdb command: 	

	(gdb) c
	Continuing.
	Can't send signals to this remote system.  
	SIGEMT not sent.
	Program received signal SIGEMT, Emulation trap.
	0x00381118 in ?? ()

In the main function beginning I call the set_debug_traps
function to initialise exceptions address. After, I call
the Breakpoint function (TRAP #1) to connect with gdb.
During the execution the program never return of the
TRAP #1 exception (it stay in the handle_exception function).

I thing the problem can be a bad address reference.

What can I do to resume the program execution ??
If somebody has any idea, thanks to thing to me :-) 

Thanks

Pascal


             reply	other threads:[~2002-08-14  9:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-14  2:34 Squal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-07  5:49 Squal
2002-08-07  7:22 ` Quality Quorum
2002-08-07  8:17 ` William A. Gatliff

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=3D5A2543.79DAA828@enssat.fr \
    --to=pmarty@enssat.fr \
    --cc=gdb@sources.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