Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Cogen <cogen@ll.mit.edu>
To: dan@cgsoftware.com
Cc: kettenis@wins.uva.nl, gdb@sourceware.cygnus.com, cogen@poblano
Subject: Re: gdb seg violation during print command
Date: Thu, 04 May 2000 12:40:00 -0000	[thread overview]
Message-ID: <200005041936.PAA09829@ll.mit.edu> (raw)
In-Reply-To: <Pine.LNX.4.10.10005041041220.27878-100000@propylaea.anduin.com>

> It's also possible the bug you are experiencing is that the compiler is
> putting the line note in the wrong place, and it's not breaking till the
> program is really done, and cerr doesn't exist properly.
> 
> Try -gdwarf-2, see if it helps.

redsavina% g++ -gdwarf-2 -o test test.cc
ld: fatal: relocation error: R_SPARC_32: file /tmp/ccwCKbbB.o:  symbol <unknown>:  offset 0xfea2c82f is non-aligned

collect2: ld returned 1 exit status
redsavina% 

Thanks for the suggestion. But as you see, it made it worse :)

-- DavidC
From dan@cgsoftware.com Thu May 04 12:45:00 2000
From: Daniel Berlin <dan@cgsoftware.com>
To: David Cogen <cogen@ll.mit.edu>
Cc: kettenis@wins.uva.nl, gdb@sourceware.cygnus.com, cogen@poblano
Subject: Re: gdb seg violation during print command
Date: Thu, 04 May 2000 12:45:00 -0000
Message-id: <Pine.LNX.4.10.10005041243050.28288-100000@propylaea.anduin.com>
References: <200005041936.PAA09829@ll.mit.edu>
X-SW-Source: 2000-05/msg00022.html
Content-length: 698

Errr, i forgot you are on a sparc.
Hmmmmm.

Try adding a line or three to main that do nothing.

On Thu, 4 May 2000, David Cogen wrote:

> > It's also possible the bug you are experiencing is that the compiler is
> > putting the line note in the wrong place, and it's not breaking till the
> > program is really done, and cerr doesn't exist properly.
> > 
> > Try -gdwarf-2, see if it helps.
> 
> redsavina% g++ -gdwarf-2 -o test test.cc
> ld: fatal: relocation error: R_SPARC_32: file /tmp/ccwCKbbB.o:  symbol <unknown>:  offset 0xfea2c82f is non-aligned
> 
> collect2: ld returned 1 exit status
> redsavina% 
> 
> Thanks for the suggestion. But as you see, it made it worse :)
> 
> -- DavidC
> 


  reply	other threads:[~2000-05-04 12:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200005041655.MAA10513@ll.mit.edu>
2000-05-04 10:41 ` Daniel Berlin
2000-05-04 10:42 ` Daniel Berlin
2000-05-04 12:40   ` David Cogen [this message]
     [not found] <66st9c39.fsf@dynamic-addr-88-42.resnet.rochester.edu>
2000-05-05 13:16 ` David Cogen
     [not found] <bt2ne3cq.fsf@dynamic-addr-88-117.resnet.rochester.edu>
2000-05-04 11:06 ` David Cogen
     [not found] <200005031637.MAA25467@ll.mit.edu>
2000-05-03 10:59 ` Mark Kettenis

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=200005041936.PAA09829@ll.mit.edu \
    --to=cogen@ll.mit.edu \
    --cc=cogen@poblano \
    --cc=dan@cgsoftware.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=kettenis@wins.uva.nl \
    /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