[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [emacs-bidi] [FWD] compiling emacs-bidi,
From: |
rs6233 |
Subject: |
Re: [emacs-bidi] [FWD] compiling emacs-bidi, |
Date: |
Sun, 14 Mar 2004 22:15:03 -0800 (PST) |
Thanks. Here is what I found:
The program dumps core on line 925 of unexelf.c (in
function unexec):
memcpy (NEW_SECTION_H (nn).sh_offset + new_base,
(caddr_t) OLD_SECTION_H (n).sh_addr,
new_data2_size);
The definitions in the beginning of unexelf.c are:
#define OLD_SECTION_H(n) \
(*(ElfW(Shdr) *) ((byte *) old_section_h +
old_file_h->e_shentsize * (n)))
#define NEW_SECTION_H(n) \
(*(ElfW(Shdr) *) ((byte *) new_section_h +
new_file_h->e_shentsize * (n)))
When I am in gdb at the unexec level, I get:
(gdb) print n
$14 = 20
(gdb) print nn
$15 = 20
(gdb) print new_section_h
$16 = (Elf32_Shdr *) 0xbee98a18
(gdb) print new_file_h
No symbol "new_file_h" in current context.
(gdb) print new_base
$17 = 0xbd6d5000 "\177ELF\001\001\001"
(gdb) print old_section_h
$18 = (Elf32_Shdr *) 0xbf34edb8
(gdb) print old_file_h
No symbol "old_file_h" in current context.
(gdb) print new_data2_size
$20 = 20204640
Any ideas? Thanks.
Rafi
--- Eli Zaretskii <address@hidden> wrote:
> > Date: Fri, 12 Mar 2004 23:12:46 -0800 (PST)
> > From: rs6233 <address@hidden>
> >
> > Dumping under names emacs and emacs-21.3.50.1
> >
> > Program received signal SIGSEGV, Segmentation
> fault.
> > 0x00c21dcc in memcpy () from /lib/tls/libc.so.6
> >
> >
> >
> >
> > When I did a backtrace, I got:
> >
> >
> >
> > #0 0x00c21dcc in memcpy () from
> /lib/tls/libc.so.6
> > #1 0x081547d2 in unexec (
> > new_name=0x97877e0
> > "/extras/emacs-bidi/emacs-bidi/src/emacs",
> > old_name=0x978780c
> > "/extras/emacs-bidi/emacs-bidi/src/temacs",
> > data_start=135852012, bss_start=0,
> entry_address=0) at unexelf.c:925
>
> This is where you should start debugging: in frame
> #1 unexelf.c called
> memcpy with bad arguments. So the first thing to do
> is to find which
> argument is bad, and then try to figure out why.
>
> Therefore, please look at line 925 of unexelf.c and
> print the values
> of the arguments it passes to memcpy. One or more
> of them should be
> wrong (e.g., NULL pointers etc.).
__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com
- Re: [emacs-bidi] [FWD] compiling emacs-bidi,, rs6233, 2004/03/10
- Re: [emacs-bidi] [FWD] compiling emacs-bidi,, Eli Zaretskii, 2004/03/13
- Re: [emacs-bidi] [FWD] compiling emacs-bidi,, rs6233, 2004/03/13
- Re: [emacs-bidi] [FWD] compiling emacs-bidi,, Eli Zaretskii, 2004/03/13
- Re: [emacs-bidi] [FWD] compiling emacs-bidi,,
rs6233 <=
- Re: [emacs-bidi] [FWD] compiling emacs-bidi,, Eli Zaretskii, 2004/03/17
- Re: [emacs-bidi] [FWD] compiling emacs-bidi,, rs6233, 2004/03/18
- Re: [emacs-bidi] [FWD] compiling emacs-bidi,, Eli Zaretskii, 2004/03/18
- Re: [emacs-bidi] [FWD] compiling emacs-bidi,, rs6233, 2004/03/18