Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Joel Soete <soete.joel@tiscali.be>
To: Carlos O'Donell <carlos@baldric.uwo.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 	RE: New glibc patches 2004-03-08, fixes GLRO changes.
Date: Sat, 13 Mar 2004 18:59:22 +0000	[thread overview]
Message-ID: <40535A0A.4020209@tiscali.be> (raw)
In-Reply-To: <20040312212012.GS24266@baldric.uwo.ca>



Carlos O'Donell wrote:
> On Fri, Mar 12, 2004 at 06:33:11PM +0100, Joel Soete wrote:
> 
>>Hmmm all output files realted to Error1 was empty because of:
>>hppa-linux-gcc -nostdlib -nostartfiles -o /Develop/parisc-linux/build/glibc/posix/tst-regex
>> -Wl,-dynamic-linker=/lib/ld.so.1
>>/Develop/parisc-linux/build/glibc/csu/crt1.o /Develop/parisc-linux/build/glibc/csu/crti.o
>>`hppa-linux-gcc --print-file-name=crtbegin.o` /Develop/parisc-linux/build/glibc/posix/tst-regex.o
>>/Develop/parisc-linux/build/glibc/rt/librt.so  -Wl,-rpath-link=/Develop/parisc-linux/build/glibc:/Develop/parisc-linux/build/glibc/math:/Develop/parisc-linux/build/glibc/elf:/Develop/parisc-linux/build/glibc/dlfcn:/Develop/parisc-linux/build/glibc/nss:
>>/Develop/parisc-linux/build/glibc/nis:/Develop/parisc-linux/build/glibc/rt:/Develop/parisc-linux/build/glibc/resolv:/Develop/parisc-linux/build/glibc/crypt:/Develop/parisc-linux/build/glibc/linuxthreads
>>/Develop/parisc-linux/build/glibc/libc.so.6 /Develop/parisc-linux/build/glibc/libc_nonshared.a
>>-lgcc `hppa-linux-gcc --print-file-name=crtend.o` /Develop/parisc-linux/build/glibc/csu/crtn.o
>>/Develop/parisc-linux/build/glibc/rt/librt.so: undefined reference to `pthread_create'
>>/Develop/parisc-linux/build/glibc/rt/librt.so: undefined reference to `_pthread_cleanup_pop'
>>/Develop/parisc-linux/build/glibc/rt/librt.so: undefined reference to `pthread_once'
>>/Develop/parisc-linux/build/glibc/rt/librt.so: undefined reference to `_pthread_cleanup_push'
>>/Develop/parisc-linux/build/glibc/rt/librt.so: undefined reference to `pthread_atfork'
>>collect2: ld returned 1 exit status
>>make[2]: *** [/Develop/parisc-linux/build/glibc/posix/tst-regex] Error 1
> 
> 
> Are you sure you thread library was built correctly?
oops, I need more check on Monday (sorry) (btw I forget to transmit you my final patch about feupdate

> Do you see those
> symbols in libpthread? All those issues are related to libpthread being
> broken somehow.
>  
> 
>>make[2]: *** [/Develop/parisc-linux/build/glibc/elf/tst-dlmodcount.out] Error 139
>>do_page_fault() pid=9891 command='ld.so.1' type=15 address=0x401aca28
>>vm_start = 0x40177000, vm_end = 0x4017c000
> 
> 
> Can you run the loader through gdb, and give an assembly dump around the
> address where it crashes?
>
No pb if gdb don't segv (but iirc that only appened with gcc-3.5) and if lucky I could also garb a bt :).

Btw in previous test, I noticed that IAOQ was for instance =0x41007293 when gdb shows me the actual address of the crash at 
'0x41007293 - 3' and I find well the corresponding code at  7290 in an 'objdump -d'. Do you know why this diff of 3?

Sorry for delay, at Monday,
	Joel

  reply	other threads:[~2004-03-13 18:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-07 13:05 [parisc-linux] glibc cvs: additional patche Joel Soete
2004-03-07 21:23 ` [parisc-linux] " Carlos O'Donell
2004-03-08  7:27   ` Joel Soete
2004-03-08 17:49     ` [parisc-linux] New glibc patches 2004-03-08, fixes GLRO changes Carlos O'Donell
2004-03-09  9:04       ` [parisc-linux] " Joel Soete
2004-03-09 13:49         ` Joel Soete
2004-03-09 15:03           ` Carlos O'Donell
2004-03-09 15:41             ` Joel Soete
2004-03-10 14:47             ` Joel Soete
2004-03-10 18:21               ` Joel Soete
2004-03-11 18:42               ` Carlos O'Donell
2004-03-12 15:32                 ` Joel Soete
2004-03-12 16:41                   ` Carlos O'Donell
2004-03-12 17:33                     ` Joel Soete
2004-03-12 21:20                       ` Carlos O'Donell
2004-03-13 18:59                         ` Joel Soete [this message]
2004-03-14 19:32                           ` Carlos O'Donell
2004-03-14 19:40                             ` Carlos O'Donell
2004-03-14 19:59                           ` Joel Soete
2004-03-14 20:12                             ` James Morrison
2004-03-15  6:31                               ` Joel Soete
2004-03-16 14:57                                 ` James Morrison
2004-03-15 17:38                             ` Joel Soete
2004-03-15 18:51                               ` Carlos O'Donell
2004-03-16  9:43                                 ` Joel Soete
2004-03-16 21:09                                   ` Carlos O'Donell
2004-03-17  8:30                                     ` Joel Soete
2004-03-18 17:59                                       ` Carlos O'Donell
2004-03-23  7:07                                   ` Joel Soete
2004-03-23 17:06                                     ` Carlos O'Donell
2004-04-01 15:14                                       ` Joel Soete
2004-04-02  5:51                                         ` Carlos O'Donell
2004-03-09 15:07           ` James Morrison
2004-03-09 15:09             ` Carlos O'Donell
2004-03-09 15:39               ` James Morrison

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=40535A0A.4020209@tiscali.be \
    --to=soete.joel@tiscali.be \
    --cc=carlos@baldric.uwo.ca \
    --cc=parisc-linux@lists.parisc-linux.org \
    /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