From: john o goyo <jog37@riddermarkfarm.ca>
To: Tom Tromey <tom@tromey.com>
Cc: gdb@sourceware.org
Subject: Re: Unable to trace assembler in GDB 14.2 on Solaris 11.3/sparc [SOLVED]
Date: Thu, 21 Mar 2024 13:27:40 -0400 [thread overview]
Message-ID: <e7fe579c-99a3-daa0-a629-f56249e1e893@riddermarkfarm.ca> (raw)
In-Reply-To: <87o7b7eegd.fsf@tromey.com>
Greetings, Tom.
On 2024-03-21 12:29, Tom Tromey wrote:
> I didn't want to let this go unanswered, but I was hoping someone more
> familiar with Solaris would reply.
>
>> I am learning Sparc assembler (mostly through Paul's book and various
>> tutorials). I built GDB 14.2 on Solaris 11.3/sparc and can debug C
>> code with no problem.
>> .section ".data"
>> hello: .asciz "Hello, World!\n"
>> .global main
>> .align 4
>> main:
> Does main end up in .data here? If so that could be the issue.
Yes -- that was exactly my mistake. I added .section ".text" before the
.global main and now main shows up as it should.
Thank you very much!
john
>
> Normally this kind of thing should work ok, as far as I know.
>
> Maybe dumping the minimal symbols ("maint print msymbols") would be
> informative.
>
> Tom
prev parent reply other threads:[~2024-03-21 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 14:50 Unable to trace assembler in GDB 14.2 on Solaris 11.3/sparc john o goyo
[not found] ` <8f334a7b-b0d8-4bee-b58a-d09526c6b0ab@redhat.com>
2024-03-18 15:12 ` john o goyo
2024-03-20 22:33 ` Unable to trace assembler in GDB 14.2 on Solaris 11.3/sparc [Solved] john o goyo
2024-03-21 16:29 ` Unable to trace assembler in GDB 14.2 on Solaris 11.3/sparc Tom Tromey
2024-03-21 17:27 ` john o goyo [this message]
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=e7fe579c-99a3-daa0-a629-f56249e1e893@riddermarkfarm.ca \
--to=jog37@riddermarkfarm.ca \
--cc=gdb@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).