From: Mike Frysinger <vapier@gentoo.org>
To: insight@sourceware.org
Cc: arkkimede <arkkimede@gmail.com>, insight@sources.redhat.com
Subject: Re: insight and nasm
Date: Thu, 21 May 2009 18:26:00 -0000 [thread overview]
Message-ID: <200905211426.16814.vapier@gentoo.org> (raw)
In-Reply-To: <e720e020905210740j4773a917p6d59e3dc78223cdd@mail.gmail.com>
On Thursday 21 May 2009 10:40:58 arkkimede wrote:
> It is possible debugging a file written for the nasm assembly with insight?
insight is merely a frontend to gdb. gdb merely cares about the debugging
information in the objects. you probably arent telling nasm to emit debugging
information.
-mike
WARNING: multiple messages have this Message-ID
From: Mike Frysinger <vapier@gentoo.org>
To: insight@sourceware.org
Cc: arkkimede <arkkimede@gmail.com>, insight@sources.redhat.com
Subject: Re: insight and nasm
Date: Sun, 24 May 2009 08:38:00 -0000 [thread overview]
Message-ID: <200905211426.16814.vapier@gentoo.org> (raw)
Message-ID: <20090524083800.1uPhRinNhrWeNE_e904KeS1XqwkJpw6Fq_ubIAAunaE@z> (raw)
In-Reply-To: <e720e020905210740j4773a917p6d59e3dc78223cdd@mail.gmail.com>
On Thursday 21 May 2009 10:40:58 arkkimede wrote:
> It is possible debugging a file written for the nasm assembly with insight?
insight is merely a frontend to gdb. gdb merely cares about the debugging
information in the objects. you probably arent telling nasm to emit debugging
information.
-mike
next prev parent reply other threads:[~2009-05-21 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 14:41 arkkimede
2009-05-21 18:26 ` Mike Frysinger [this message]
2009-05-24 8:38 ` 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=200905211426.16814.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=arkkimede@gmail.com \
--cc=insight@sources.redhat.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).