Hi Dan,
I think that the simplest change we could make would be to have BFD
detect object files with a magic number of 0x188 and then have it
issue an error message along the lines of "please decompress this file
before passing it to BFD". What do you think ?
This makes sense, so I've atta
The i686-pc-linux-gnu build of the assembler from binutils 2.16 crx-port
creates a segmentation fault with the assembly file below. This time the
problem is located in libiberty/xexit.c where the function pointer named
_xexit_cleanup in line 44 is NOT initialized to NULL.
The following patch for x
The i686-pc-linux-gnu build of the assembler from binutils 2.16 crx-port
creates a segmentation fault with the assembly file below. This time the
problem is located in libiberty/xexit.c where the function pointer named
_xexit_cleanup in line 44 is NOT initialized to NULL.
The following patch for x
--
What|Removed |Added
Summary|Segmentation fault in |Buffer overflow in tc-crx.c
|libiberty/xexit.c:51|
http://sources.redhat.com/bugzil
--- Additional Comments From amodra at bigpond dot net dot au 2005-07-14
14:34 ---
No, this is a buffer overflow of gas/config/tc-crx.c:ins_parse in reset_vars.
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=1069
--- You are receiving this mail because: ---
You are on
Hi Guys,
Alan wrote:
No, this is a buffer overflow of gas/config/tc-crx.c:ins_parse in reset_vars.
And I am applying this patch to stop the overflow and prevent the
seg-fault. (This also makes the patch applied for 1063 redundant, but
that should not matter).
Cheers
Nick
gas/ChangeLog
--- Additional Comments From nickc at redhat dot com 2005-07-14 15:36
---
Subject: Re: Segmentation fault in libiberty/xexit.c:51
Hi Guys,
> Alan wrote:
> No, this is a buffer overflow of gas/config/tc-crx.c:ins_parse in reset_vars.
And I am applying this patch to stop the overflow a
--- Additional Comments From nickc at redhat dot com 2005-07-14 15:37
---
Patch applied
--
What|Removed |Added
Status|NEW |RESOLVED
Either cpp or the assembler is at fault in this problem.
Using gcc on the following code causes the assembler to issue
the error "too many positional arguments"
# Load immediate word, has to be done with 2 instructions
.macro lwi reg,val
lis \reg,[EMAIL PROTECTED]
ori \reg,\reg,[EM
--
What|Removed |Added
BugsThisDependsOn||1031
http://sources.redhat.com/bugzilla/show_bug.cgi?id=1021
--- You are receiving this mail because: ---
--
What|Removed |Added
OtherBugsDependingO||1021
nThis||
http://sources.redhat.com/bugzilla/show_bug.cgi?id=1031
--- Additional Comments From ebotcazou at gcc dot gnu dot org 2005-07-14
16:22 ---
What has changed in libdl between Solaris 9 and Solaris 10 is that the stubs for
dlopen, dlclose, etc present on Solaris 9:
poog% /opt/build/eric/local/bin/objdump -T /usr/lib/libdl.so.1
/usr/lib/libdl.s
--- Additional Comments From ian at airs dot com 2005-07-14 16:45 ---
Your patch can not be correct, because global variables are implicitly
initialized to NULL. There must be something else going on. Can you show
precisely how you configured the binutils? Is this unmodified FSF binuti
--- Additional Comments From ian at airs dot com 2005-07-14 16:46 ---
I see now that this was duplicated as PR 1069, and fixed there.
*** This bug has been marked as a duplicate of 1069 ***
--
What|Removed |Added
--
--- Additional Comments From ian at airs dot com 2005-07-14 16:46 ---
*** Bug 1068 has been marked as a duplicate of this bug. ***
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=1069
--- You are receiving this mail because: ---
You are on the CC list for the bug, or ar
15 matches
Mail list logo
