Re: [FWD] compiling emacs-bidi,

Below is the result of the two commands. 

Program received signal SIGSEGV, Segmentation fault.
0x00c21dcc in memcpy () from /lib/tls/libc.so.6
(gdb) up
#1  0x081547d2 in unexec (
    new_name=0x8a4c7a8
"/extras/emacs-bidi/emacs-bidi/src/emacs",
    old_name=0x8a4c7d4
"/extras/emacs-bidi/emacs-bidi/src/temacs",
    data_start=135852012, bss_start=0,
entry_address=0) at unexelf.c:925
925               memcpy (NEW_SECTION_H (nn).sh_offset
+ new_base,
(gdb) info line unexelf.c:925
Line 925 of "unexelf.c" starts at address 0x81547a9
<unexec+3505>
   and ends at 0x81547ac <unexec+3508>.
(gdb) disassemble 0x81547a9 0x81547ac
Dump of assembler code from 0x81547a9 to 0x81547ac:
0x081547a9 <unexec+3505>:       add    $0xc,%esp
End of assembler dump.



Rafi

--- Eli Zaretskii <[email protected]> wrote:
> > Date: Wed, 17 Mar 2004 22:12:04 -0800 (PST)
> > From: rs6233 <[email protected]>
> > 
> > (gdb) print (*(ElfW(Shdr) *) ((byte *)
> old_section_h +
> > old_file_h->e_shentsize * (n))).sh_addr
> > No symbol "ElfW" in current context.
> 
> It sounds like there are too many variables in
> registers.  Let's see
> what happens on the machine code level.
> 
> The command
> 
>   (gdb) info line unexelf.c:925
> 
> should print the range of addresses for the code
> generated from line
> 925 of unexelf.c.  After that, the command
> 
>   (gdb) disassemble n1 n2
> 
> where n1 and n2 are the two addresses printed by
> "info line", will
> display the machine code for line 925.  Please post
> the results of
> these 2 commands.


__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com