From: "Lev Assinovsky" <LAssinovsky@algorithm.aelita.com>
To: "Andrew Cagney" <ac131313@redhat.com>
Cc: <gdb@sources.redhat.com>
Subject: RE: pa-risc 1.1 and breakpoint
Date: Thu, 04 Sep 2003 09:13:00 -0000 [thread overview]
Message-ID: <3F6F4712B759A34ABD453A8B39C10D62F60C0B@bagman.edm.com> (raw)
I found how work around.
Instead of "continue" I "jump"
to the line following "break".
Now I have mutch bigger problem!!
gdb doesn't see the shared libraries loaded explicitly!
I need help!!
Thanks,
----
Lev Assinovsky
Aelita Software Corporation
O&S Core Division, Programmer
ICQ# 165072909
> -----Original Message-----
> From: Andrew Cagney [mailto:ac131313@redhat.com]
> Sent: Thursday, September 04, 2003 2:51 AM
> To: Lev Assinovsky
> Cc: gdb@sources.redhat.com
> Subject: Re: pa-risc 1.1 and breakpoint
>
>
> > Hello all!
> > Sometimes I need to insert breakpoint right in my gcc
> program code.
> > For Solaris x86 I use __asm__( "int $3" );
> > When I run the program with gdb it stops and I can debug
> and continue of course.
> > I tried __asm__( "break 4,8" ) for pa-risc 1.1 but unsuccessfully.
> > gdb stops but can't continue.
> >
> > What must be the right instruction sequence for pa-risc 1.1?
> > Any help will be greatly appreciated!
>
> I don't know that this is supported. However, you could investigate
> permenant breakpoints.
>
> Andrew
>
>
>
next reply other threads:[~2003-09-04 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 9:13 Lev Assinovsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-05 11:39 Lev Assinovsky
2003-09-03 22:50 ` Andrew Cagney
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=3F6F4712B759A34ABD453A8B39C10D62F60C0B@bagman.edm.com \
--to=lassinovsky@algorithm.aelita.com \
--cc=ac131313@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).