From: "Dave Korn" <dave.korn@artimi.com>
To: "'Joze Turkl'" <joze.turkl@uni-mb.si>
Cc: <insight@sources.redhat.com>
Subject: RE: Question
Date: Fri, 06 Jan 2006 10:56:00 -0000 [thread overview]
Message-ID: <SERRANOtFBNlJbSorxT0000024c@SERRANO.CAM.ARTIMI.COM> (raw)
In-Reply-To: <43BE49A1.9070906@uni-mb.si>
Joze Turkl wrote:
[ Joze, please remember to keep the mailing list in the To: line; I'm not the
only person on the list, and there are others there who understand ARM better
than me, and who might have seen your problem before. ]
>>> I would like to debug code with insight but when I try to run
>>> executable(.elf file) I get error 193 (error creating process).
> System details:
>
> WinARM *Version 20050819*:
>
> * GNU-C/C++-Compiler (cross compiler/linker/assembler arm-elf-*)
> Version 4.0.1 incl. stdlib3. Compiled from the FSF-Sources
> <http://www.gnu.org> . The configuration supports ARM-Mode,
> Thumb-Mode and Mixed(ARM/Thumb)-Mode, little/big-endian and
> floating point-emulation (all targets which are also supported by
> gnuarm)
> * GNU-Binutils Version Version 2.15.94 (from mingw)
> <http://www.mingw.org>
> * newlib <http://sources.redhat.com/newlib/> Version 1.13.0 (build
> for reentrant syscalls)
> * newlib-lpc
> <http://www.aeolusdevelopment.com/Articles/download.html> Rel.4
> (reentrant functions to fill newlib-stubs for Philips LPCs)
> * GNU-*Utils* do support the compiler/linker (make
> <http://unxutils.sourceforge.net/>, sh
> <ftp://ftp.blarg.net/users/amol/zsh/> etc. all Win32-native)
> * ARM header-files (register-defintions) from gnuarm.org
> <http://www.gnuarm.org>
> * *Example applications* with full source-code, makefiles,
> linker-scripts and startup-code (partly tested with Philips
> LPC2106 and LPC2129 ARM7TDMI-S and AT91SAM7S64 ARM7TDMI)
> * Programmers Notepad <http://www.pnotepad.org/> Editor Version
> 2.0.5.48
> * The lpc21isp <http://www.engelschall.com/%7Emartin/lpc21xx/isp/>
> in-system-programming-software for Philips LPC2xxx and the Analog
> Devices ADUC 70xx family by Martin Maurer. Included: Version 1.27
> and Version 2.01 (BETA!)
> * Bray Terminal <http://bray.velenje.cx/avr/terminal/>
> * Insight-GDB 5.2.1 (old) - Win32-Native (devkit.tk
> <http://www.devkit.tk/>)
> * GDB (command-line without Insight) Version 6.3.50 from
> Codesourcery <http://www.codesourcery.com/>
> * Setup-Exe of Macraigor's OCDRemote
> <http://www.macraigor.com/full_gnu.htm>
>
>
> With programers notepad I compile some example.
> for debugging I use Insight GNU gdb 6.3.50.20051115-cvs.
.. and in your other post you said
>+ output form insight console : error creating process
>C:\winarm\exaples\something\something.elf (error 193)
Hmm. That's the exact same error I get when I try to run a cross-compiled
ELF executable with my cygwin native insight.
Are you _completely_ sure you're invoking the ARM cross-debugger
arm-elf-insight.exe and not the cygwin native x86 debugger under the plain
insight.exe name?
cheers,
DaveK
--
Can't think of a witty .sigline today....
next parent reply other threads:[~2006-01-06 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43BE49A1.9070906@uni-mb.si>
2006-01-06 10:56 ` Dave Korn [this message]
2006-01-06 7:57 Question Joze Turkl
2006-01-06 10:15 ` Question Dave Korn
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=SERRANOtFBNlJbSorxT0000024c@SERRANO.CAM.ARTIMI.COM \
--to=dave.korn@artimi.com \
--cc=insight@sources.redhat.com \
--cc=joze.turkl@uni-mb.si \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).