From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [rft/symtab] Check the sizes of minimal symbols
Date: Sun, 09 Jul 2006 20:36:00 -0000 [thread overview]
Message-ID: <20060709203557.GA21606@nevyn.them.org> (raw)
In-Reply-To: <200607092026.k69KQKQg027664@elgar.sibelius.xs4all.nl>
On Sun, Jul 09, 2006 at 10:26:20PM +0200, Mark Kettenis wrote:
> > Date: Thu, 6 Jul 2006 23:54:20 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > This is something I've been meaning to do for years, on general principle.
> > Much to my surprise it did very good things (~ 15% fails fixed) for my
> > native amd64 test run, too, so I have a good example to illustrate with.
> >
> > In ELF, one of the properties of a symbol is its size. If left unspecified,
> > the size is treated as zero. Some hand-written code may lack .size, but
> > most compiled code will have it.
>
> Cool! Unfortunately there seems to be something wrong with the patch.
> On i386-pc-openbsd3.9, a gdb segfaults when I try to run anything.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x1c0066a8 in lookup_minimal_symbol_by_pc_section (pc=469800299,
> section=0x800e95fc) at ../../../src/gdb/gdb/minsyms.c:535
> 535 if (MSYMBOL_SIZE (&msymbol[hi]) != 0
I'm just guessing here but... is hi == -1 when that happens? Does
adding "hi >= 0 &&" to the front of that if statement help?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-07-09 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 3:54 Daniel Jacobowitz
2006-07-09 20:26 ` Mark Kettenis
2006-07-09 20:36 ` Daniel Jacobowitz [this message]
2006-07-11 22:01 ` Mark Kettenis
2006-07-11 22:48 ` Daniel Jacobowitz
2006-07-13 23:24 ` Mark Kettenis
2006-07-19 2:17 ` Daniel Jacobowitz
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=20060709203557.GA21606@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.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