Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
gnu.gdb.bug
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
watchpoints don't trigger on UltraSPARC?
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Craig Burley  
View profile  
 More options Feb 26 1997, 3:00 am
Newsgroups: gnu.gdb.bug
From: bur...@gnu.ai.mit.edu (Craig Burley)
Date: 1997/02/26
Subject: watchpoints don't trigger on UltraSPARC?
Print | Individual message | Show original | Report this message | Find messages by this author

I just noticed, while debugging a huge executable, that
I couldn't get watchpoints to actually trigger while
working on an UltraSPARC running Solaris 2.5.1 running
gdb-4.16 built on the same machine.

Trying "p *(some address)" would show a value.  Then,
I'd do "watch *(some address)" and "continue", and
it would act normal (take a lot longer to run, etc.).

Next thing is the executable being debugged would crash
(that's why I was debugging it ;-), and I'd do
"p *(some address)" again, the value would be different,
but no watch point.

The work-around was simple -- I switched to a SuperSPARC
running Solaris 2.5.1 on the same network.  Using gdb-4.15.1
or something like that, the same commands worked fine, though
of course the Super took longer.

If you don't already know about this problem, and need me
to get you sample executables and command sequences, please
just let me know where to shovel the huge executable (probably
over 8MB) to you.  (It's the GNU Fortran compiler module,
called f771.)

I'd say more, but have the feeling the problem is already
known about and probably fixed, and am in crunch mode trying
to release the newest g77.  But I'll make time to help improve
gdb by submitting a better bug report if that would help!

        tq vm, (burley)


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google