FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Crash Utility

 
 
LinkBack Thread Tools
 
Old 07-19-2012, 12:20 PM
Adrien Kunysz
 
Default timeout in eppic.mk

Different network topologies/setups will have different failure modes.
If you want to dig into this I would suggest getting a network capture
(tcpdump -s0) at the time of the problem so we can see exactly at what
level it is timing out. That said I am not sure the crash build
scripts should really have to deal with this kind of things.

On Thu, Jul 19, 2012 at 6:40 AM, Karlsson, Jan
<Jan.Karlsson@sonymobile.com> wrote:
> Hi
>
> I searched for information on this and it seems that the timeout is dependent on Linux installation. 10 sec seems also to be a not uncommon default timeout. If you want to set the timeout you can use the -W option.
>
> ping -c 1 -W 1 code.google.com
>
> will timeout after 1 sec for me.
>
> Jan
>
>
> Jan Karlsson
> Senior Software Engineer
> MIB
>
> Sony Mobile Communications
> Tel: +46703062174
> sonymobile.com
>
>
>
> -----Original Message-----
> From: crash-utility-bounces@redhat.com [mailto:crash-utility-bounces@redhat.com] On Behalf Of Dave Anderson
> Sent: onsdag den 18 juli 2012 15:19
> To: Discussion list for crash utility usage, maintenance and development
> Subject: Re: [Crash-utility] timeout in eppic.mk
>
>
>
> ----- Original Message -----
>> Thanks Dave, the patch works as intended for me. I now get a 10 sec
>> timeout instead of the 10 min timeout I had before, followed by the
>> message "failed to pull epic code .....".
>
> Right, although I'm surprised that you have a 10 second timeout.
>
> If I put in a valid name of a machine that I've shut down, the "ping -c 1 <name>" only takes about 1 second to return a failure.
>
> Anyway, I'll queue that change for crash-6.0.9.
>
> Thanks,
> Dave
>
>
> --
> Crash-utility mailing list
> Crash-utility@redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility
>
> --
> Crash-utility mailing list
> Crash-utility@redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 
Old 07-19-2012, 12:47 PM
Dave Anderson
 
Default timeout in eppic.mk

----- Original Message -----
> Different network topologies/setups will have different failure modes.
> If you want to dig into this I would suggest getting a network capture
> (tcpdump -s0) at the time of the problem so we can see exactly at what
> level it is timing out. That said I am not sure the crash build
> scripts should really have to deal with this kind of things.

Right -- I think I'll just leave it as is (i.e. without -W), and let
it timeout based upon the host machine's setup. It's not that big a
deal, and Jan was happy enough with his 10-second timeout vs. the
annoying 10-minute git command timeout.

Dave


> On Thu, Jul 19, 2012 at 6:40 AM, Karlsson, Jan
> <Jan.Karlsson@sonymobile.com> wrote:
> > Hi
> >
> > I searched for information on this and it seems that the timeout is
> > dependent on Linux installation. 10 sec seems also to be a not
> > uncommon default timeout. If you want to set the timeout you can
> > use the -W option.
> >
> > ping -c 1 -W 1 code.google.com
> >
> > will timeout after 1 sec for me.
> >
> > Jan

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 
Old 07-31-2012, 12:58 PM
Per Fransson
 
Default timeout in eppic.mk

Hi,

On Thu, Jul 19, 2012 at 2:47 PM, Dave Anderson <anderson@redhat.com> wrote:
>
>
> ----- Original Message -----
>> Different network topologies/setups will have different failure modes.
>> If you want to dig into this I would suggest getting a network capture
>> (tcpdump -s0) at the time of the problem so we can see exactly at what
>> level it is timing out. That said I am not sure the crash build
>> scripts should really have to deal with this kind of things.
>
> Right -- I think I'll just leave it as is (i.e. without -W), and let
> it timeout based upon the host machine's setup. It's not that big a
> deal, and Jan was happy enough with his 10-second timeout vs. the
> annoying 10-minute git command timeout.
>
> Dave
>

Here's an alternative patch for your consideration, which makes it
possible to point to e.g. a local eppic git.

It also builds ARM with '-m32'. This change is not enough to achieve
that however. Similar tweaks are needed in eppic itself.

Regards,
Per
--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 
Old 08-07-2012, 07:56 PM
Dave Anderson
 
Default timeout in eppic.mk

----- Original Message -----
> Hi,
>
> On Thu, Jul 19, 2012 at 2:47 PM, Dave Anderson <anderson@redhat.com>
> wrote:
> >
> >
> > ----- Original Message -----
> >> Different network topologies/setups will have different failure modes.
> >> If you want to dig into this I would suggest getting a network capture
> >> (tcpdump -s0) at the time of the problem so we can see exactly at what
> >> level it is timing out. That said I am not sure the crash build
> >> scripts should really have to deal with this kind of things.
> >
> > Right -- I think I'll just leave it as is (i.e. without -W), and let
> > it timeout based upon the host machine's setup. It's not that big a
> > deal, and Jan was happy enough with his 10-second timeout vs. the
> > annoying 10-minute git command timeout.
> >
> > Dave
> >
>
> Here's an alternative patch for your consideration, which makes it
> possible to point to e.g. a local eppic git.
>
> It also builds ARM with '-m32'. This change is not enough to achieve
> that however. Similar tweaks are needed in eppic itself.
>
> Regards,
> Per

Per,

Sorry I got to Cliff's patch before yours -- so can you rework
your patch using the version of eppic.mk that is attached to:

Re: [Crash-utility] [PATCH] allow various git command locations
https://www.redhat.com/archives/crash-utility/2012-August/msg00012.html

Thanks,
Dave

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 
Old 08-08-2012, 05:59 AM
"Karlsson, Jan"
 
Default timeout in eppic.mk

To avoid all problems with the git command one possibility is to remove it completely from the make file. Let the users that want to build the eppic extension manually perform "git clone" once to download the software. I think that I would prefer that solution.

Jan

Jan Karlsson
Senior Software Engineer
MIB
*
Sony Mobile Communications
Tel: +46703062174
sonymobile.com
*


-----Original Message-----
From: crash-utility-bounces@redhat.com [mailto:crash-utility-bounces@redhat.com] On Behalf Of Dave Anderson
Sent: tisdag den 7 augusti 2012 21:56
To: Discussion list for crash utility usage, maintenance and development
Subject: Re: [Crash-utility] timeout in eppic.mk



----- Original Message -----
> Hi,
>
> On Thu, Jul 19, 2012 at 2:47 PM, Dave Anderson <anderson@redhat.com>
> wrote:
> >
> >
> > ----- Original Message -----
> >> Different network topologies/setups will have different failure modes.
> >> If you want to dig into this I would suggest getting a network
> >> capture (tcpdump -s0) at the time of the problem so we can see
> >> exactly at what level it is timing out. That said I am not sure the
> >> crash build scripts should really have to deal with this kind of things.
> >
> > Right -- I think I'll just leave it as is (i.e. without -W), and let
> > it timeout based upon the host machine's setup. It's not that big a
> > deal, and Jan was happy enough with his 10-second timeout vs. the
> > annoying 10-minute git command timeout.
> >
> > Dave
> >
>
> Here's an alternative patch for your consideration, which makes it
> possible to point to e.g. a local eppic git.
>
> It also builds ARM with '-m32'. This change is not enough to achieve
> that however. Similar tweaks are needed in eppic itself.
>
> Regards,
> Per

Per,

Sorry I got to Cliff's patch before yours -- so can you rework your patch using the version of eppic.mk that is attached to:

Re: [Crash-utility] [PATCH] allow various git command locations
https://www.redhat.com/archives/crash-utility/2012-August/msg00012.html

Thanks,
Dave

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 
Old 08-08-2012, 12:53 PM
Dave Anderson
 
Default timeout in eppic.mk

----- Original Message -----
> To avoid all problems with the git command one possibility is to
> remove it completely from the make file. Let the users that want to
> build the eppic extension manually perform "git clone" once to
> download the software. I think that I would prefer that solution.
>
> Jan

Aside from the small delay that you see with your site's ping of google.com,
I think with Per's and Cliff's suggestions, we're handling all the "problems"
pretty well here, aren't we? I actually think the new scheme is pretty slick...

Dave

> Jan Karlsson
> Senior Software Engineer
> MIB
> *
> Sony Mobile Communications
> Tel: +46703062174
> sonymobile.com
> *
>
>
> -----Original Message-----
> From: crash-utility-bounces@redhat.com
> [mailto:crash-utility-bounces@redhat.com] On Behalf Of Dave Anderson
> Sent: tisdag den 7 augusti 2012 21:56
> To: Discussion list for crash utility usage, maintenance and
> development
> Subject: Re: [Crash-utility] timeout in eppic.mk
>
>
>
> ----- Original Message -----
> > Hi,
> >
> > On Thu, Jul 19, 2012 at 2:47 PM, Dave Anderson
> > <anderson@redhat.com>
> > wrote:
> > >
> > >
> > > ----- Original Message -----
> > >> Different network topologies/setups will have different failure
> > >> modes.
> > >> If you want to dig into this I would suggest getting a network
> > >> capture (tcpdump -s0) at the time of the problem so we can see
> > >> exactly at what level it is timing out. That said I am not sure
> > >> the
> > >> crash build scripts should really have to deal with this kind of
> > >> things.
> > >
> > > Right -- I think I'll just leave it as is (i.e. without -W), and
> > > let
> > > it timeout based upon the host machine's setup. It's not that
> > > big a
> > > deal, and Jan was happy enough with his 10-second timeout vs. the
> > > annoying 10-minute git command timeout.
> > >
> > > Dave
> > >
> >
> > Here's an alternative patch for your consideration, which makes it
> > possible to point to e.g. a local eppic git.
> >
> > It also builds ARM with '-m32'. This change is not enough to
> > achieve
> > that however. Similar tweaks are needed in eppic itself.
> >
> > Regards,
> > Per
>
> Per,
>
> Sorry I got to Cliff's patch before yours -- so can you rework your
> patch using the version of eppic.mk that is attached to:
>
> Re: [Crash-utility] [PATCH] allow various git command locations
> https://www.redhat.com/archives/crash-utility/2012-August/msg00012.html
>
> Thanks,
> Dave
>
> --
> Crash-utility mailing list
> Crash-utility@redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility
>
> --
> Crash-utility mailing list
> Crash-utility@redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility
>

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 
Old 08-09-2012, 07:04 PM
Dave Anderson
 
Default timeout in eppic.mk

----- Original Message -----
>
>
> ----- Original Message -----
> > Hi,
> >
> > Here's an alternative patch for your consideration, which makes it
> > possible to point to e.g. a local eppic git.
> >
> > It also builds ARM with '-m32'. This change is not enough to achieve
> > that however. Similar tweaks are needed in eppic itself.
> >
> > Regards,
> > Per
>
> Per,
>
> Sorry I got to Cliff's patch before yours -- so can you rework
> your patch using the version of eppic.mk that is attached to:
>
> Re: [Crash-utility] [PATCH] allow various git command locations
> https://www.redhat.com/archives/crash-utility/2012-August/msg00012.html
>
> Thanks,
> Dave

OK, I've shoehorned the EPPIC_GIT_URL environment variable check
into eppic.mk.

But for now I'm leaving out your -m32 addition for ARM builds
until there's a complete solution for ARM. Note that when I
put the -m32 patch in place, the compile fails when building
ARM on an x86_64 host:

gcc -g -I.. -Ieppic/libeppic -I../gdb-7.3.1/bfd -I../gdb-7.3.1/include -I../gdb-7.3.1/gdb -I../gdb-7.3.1/gdb/config -I../gdb-7.3.1/gdb/common -I../gdb-7.3.1 -nostartfiles -shared -rdynamic -o eppic.so eppic/applications/crash/eppic.c -fPIC -DARM -m32 -DGDB_7_3_1 -Leppic/libeppic -leppic
eppic/applications/crash/eppic.c: In function ‘apigetval’:
eppic/applications/crash/eppic.c:474: warning: cast from pointer to integer of different size
/usr/bin/ld: skipping incompatible eppic/libeppic/libeppic.a when searching for -leppic
/usr/bin/ld: cannot find -leppic
collect2: ld returned 1 exit status
make[4]: [eppic.so] Error 1 (ignored)

whereas without the -m32 at least it builds something (albeit probably useless).

Thanks,
Dave

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 
Old 08-13-2012, 09:17 AM
Per Fransson
 
Default timeout in eppic.mk

> ----- Original Message -----
>>
>>
>> ----- Original Message -----
>> > Hi,
>> >
>> > Here's an alternative patch for your consideration, which makes it
>> > possible to point to e.g. a local eppic git.
>> >
>> > It also builds ARM with '-m32'. This change is not enough to achieve
>> > that however. Similar tweaks are needed in eppic itself.
>> >
>> > Regards,
>> > Per
>>
>> Per,
>>
>> Sorry I got to Cliff's patch before yours -- so can you rework
>> your patch using the version of eppic.mk that is attached to:
>>
>> Re: [Crash-utility] [PATCH] allow various git command locations
>> https://www.redhat.com/archives/crash-utility/2012-August/msg00012.html
>>
>> Thanks,
>> Dave
>
> OK, I've shoehorned the EPPIC_GIT_URL environment variable check
> into eppic.mk.
>

Sorry I took so long. Vacation... =o)

So, you already put it in there? Thanks.

> But for now I'm leaving out your -m32 addition for ARM builds
> until there's a complete solution for ARM. Note that when I
> put the -m32 patch in place, the compile fails when building
> ARM on an x86_64 host:
>
> gcc -g -I.. -Ieppic/libeppic -I../gdb-7.3.1/bfd -I../gdb-7.3.1/include -I../gdb-7.3.1/gdb -I../gdb-7.3.1/gdb/config -I../gdb-7.3.1/gdb/common -I../gdb-7.3.1 -nostartfiles -shared -rdynamic -o eppic.so eppic/applications/crash/eppic.c -fPIC -DARM -m32 -DGDB_7_3_1 -Leppic/libeppic -leppic
> eppic/applications/crash/eppic.c: In function ‘apigetval’:
> eppic/applications/crash/eppic.c:474: warning: cast from pointer to integer of different size
> /usr/bin/ld: skipping incompatible eppic/libeppic/libeppic.a when searching for -leppic
> /usr/bin/ld: cannot find -leppic
> collect2: ld returned 1 exit status
> make[4]: [eppic.so] Error 1 (ignored)
>
> whereas without the -m32 at least it builds something (albeit probably useless).
>

I think we might have a catch 22 on our hands. The reason it fails is
that the eppic library doesn't get built with -m32, but if we start by
modifying the eppic git the build will fail because eppic is 32 bit
and the crash extension is 64 bit. I've attached the change I made to
the eppic git.

/Per

> Thanks,
> Dave
>
> --
> Crash-utility mailing list
> Crash-utility@redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility
--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 

Thread Tools




All times are GMT. The time now is 10:33 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org