Re: make cores on 5.4-RELEASE amd64 but not on i386, need a maintainer.

From: Julian H. Stacey (jhs_at_flat.berklix.net)
Date: 05/30/05

  • Next message: Kris Kennaway: "Re: .depend line 264: Inconsistent operator for ipf"
    To: Harti Brandt <harti@freebsd.org>
    Date: Mon, 30 May 2005 20:24:07 +0200
    
    

    Harti Brandt wrote:
    > On Mon, 30 May 2005, Julian Stacey wrote:
    >
    > JS>Any make maintainers reading this ? ... I attach a gdb backtrace.
    >
    > yes.
    >
    > JS>
    > JS>Make cores on 5.4-RELEASE amd64 but not on i386. With a virgin
    > JS>unhacked release-5.4 make executable, as built by a couple
    > JS>of `make worlds'. The hardware is OK, no other troubles.
    > JS>
    > JS>I could try strip & mail a minimal uuencoded tar.gz to
    > JS>provoke the core, but that's a little tricky:
    > JS> - Data tree is not /usr/src, but my personal data.
    > JS> - Some of my macros are also needed & some of my tools, but
    > JS> all sources for those are public on the web.
    > JS> - A recipient would need a login on an amd64 machine.
    > JS> Mine's behind a firewall.
    > JS>
    > JS>#0 0x000000000043b2a2 in memcpy ()
    > JS>#1 0x00000000004122e0 in SuffFindNormalDeps (gn=0x579d80, slst=0x561200)
    > JS> at suff.c:1797
    >
    > This could be a hint to the bug in suffix parsing that Matt found some
    > time ago. Is there any chance you can test this with a make from -current?

    Sure, I forgot to do that before posting, Thanks, done.
    I just built make from
            FreeBSD/branches/-current/src/usr.bin/make
    with a CTM date stamp on last delta received of
            214243 May 30 10:05 src-cur.6870.gz (TZ=GMT+01:00)
    & built on my 5.4-RELEASE based system (ie libs inc/ & kernel = 5.4).

    Using current make it does Not Segmentation fault,
    using 5.4 release make it does Segmentation fault.

    So it seems its's a cleared bug :-) Don't know if that's what
    you were expecting.
    What I've submited might at best now just be used as something for a
    regression test, (though it calls my make macros & builds tools &
    includes variables from other inc/Makefile type stuff, so Not a
    nice easy self contained reegression test.

    > I'll have a look tomorrow.

    Thanks.
    If you want me to test anything, shout.
    My Makefile structure will change later, & it may then be
    hard to tickle this bug again, but I'll keep a frozen version for
    a while in case needed.

    > harti
    >
    > JS>#2 0x0000000000412c09 in SuffFindDeps (gn=0x579d80, slst=0x561200)
    > JS> at suff.c:2167
    > JS>#3 0x0000000000412aac in Suff_FindDeps (gn=0x579d80) at suff.c:2115
    > JS>#4 0x0000000000402a40 in CompatMake (gnp=0x579d80, pgnp=0x570980)
    > JS> at compat.c:453
    > JS>#5 0x0000000000419224 in Lst_ForEachFrom (l=0x5754c0, ln=0x58a2a0,
    > JS> proc=0x4029d0 <CompatMake>, d=0x570980)
    > JS> at /usr1/5.4-RELEASE/src/usr.bin/make/lst.lib/lstForEachFrom.c:94
    > JS>#6 0x00000000004191b0 in Lst_ForEach (l=0x5754c0, proc=0x4029d0 <CompatMake>,
    > JS> d=0x570980) at /usr1/5.4-RELEASE/src/usr.bin/make/lst.lib/lstForEach.c:73
    > JS>#7 0x0000000000402a56 in CompatMake (gnp=0x570980, pgnp=0x570880)
    > JS> at compat.c:454
    > JS>#8 0x0000000000419224 in Lst_ForEachFrom (l=0x575100, ln=0x57d680,
    > JS> proc=0x4029d0 <CompatMake>, d=0x570880)
    > JS> at /usr1/5.4-RELEASE/src/usr.bin/make/lst.lib/lstForEachFrom.c:94
    > JS>#9 0x00000000004191b0 in Lst_ForEach (l=0x575100, proc=0x4029d0 <CompatMake>,
    > JS> d=0x570880) at /usr1/5.4-RELEASE/src/usr.bin/make/lst.lib/lstForEach.c:73
    > JS>#10 0x0000000000402a56 in CompatMake (gnp=0x570880, pgnp=0x570880)
    > JS> at compat.c:454
    > JS>#11 0x0000000000402f79 in Compat_Run (targs=0x587240) at compat.c:701
    > JS>#12 0x000000000040bfbd in main (argc=1, argv=0x7fffffffdcf0) at main.c:897
    > JS>
    > JS>-
    > JS>Julian Stacey Net & Sys Eng Consultant, Munich http://berklix.com
    > JS> Mail in Ascii (Html=Spam). Ihr Rauch = mein allergischer Kopfschmerz.
    > JS>_______________________________________________
    > JS>freebsd-current@freebsd.org mailing list
    > JS>http://lists.freebsd.org/mailman/listinfo/freebsd-current
    > JS>To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    > JS>
    > JS>
    > JS>
    >
    >

    -
    Julian Stacey Net & Sys Eng Consultant, Munich http://berklix.com
    Mail in Ascii (Html=Spam). Ihr Rauch = mein allergischer Kopfschmerz.
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  • Next message: Kris Kennaway: "Re: .depend line 264: Inconsistent operator for ipf"

    Relevant Pages

    • Re: RFID chip barcodes can carry a virus
      ... hardware and firmware for that matter) can be described as a "bug". ... We are not talking about vulnerabilities here. ...
      (misc.survivalism)
    • Re: Anthonys drive issues.Re: ssh password delay
      ... What makes it a _bug_? ... or approached the hardware in a way that made the modifications ... > at work which has a modded microcode in an Adaptec 2940U adapter card ... > spew errors) This is the same scsi chipset as Anthonys Vectra. ...
      (freebsd-questions)
    • RE: Anthonys drive issues.Re: ssh password delay
      ... The dmesg you sent indicated that the 2 disks were negotiating at ... > possible cause in the universe before blaming it on FreeBSD. ... to take the risk of it being hardware, ... believe is that it's a bug in the FreeBSD driver. ...
      (freebsd-questions)
    • Re: hardware errors, do C and Forth need different things in hardware?
      ... do what the comment says or it is a bug that *always* needs fixing ... maybe even needing hardware traps?" ... Any functioning C compiler will generate code that does exactly what it says. ... Your code is clearly a bug in *some* cases, but since C can't tell if this is a bug or the actual intent of the programmer, C will faithfully compile the code to do what the programmer wants-- just like Forth. ...
      (comp.lang.forth)
    • Re: how important is an emulator to an embedded engineer?
      ... If you are strapped for resources, an emulator ... The emulator itself may have hardware and/or software/firmware ... understand the design, the technology and the behaviours of the ... If you suspect a bug, write a short, concise test ...
      (comp.arch.embedded)