Hi Felix,
On Fri, Aug 1, 2014 at 1:27 PM, Felix Fietkau wrote:
> On 2014-07-24 17:26, Helmut Schaa wrote:
>> Introduce a new config symbol EXTRACT_DEBUGINFO to extract debuginfo
>> from all binaries. This depends on USE_STRIP and DEBUG.
>>
>> The debuginfo of all packages will be extracted from t
On 2014-08-03 08:46, Alexandru Ardelean wrote:
> Well, this is useful because you have your FW build and your symbols
> right next to it for each build.
>
> Then, you can store them somewhere (FW + debug symbols) and if you get a
> crash/segfault on a specific build number you're covered because y
Well, this is useful because you have your FW build and your symbols right
next to it for each build.
Then, you can store them somewhere (FW + debug symbols) and if you get a
crash/segfault on a specific build number you're covered because you can
pull symbols and use them on coredumps for that sp
On 08/01/2014 11:27 AM, Felix Fietkau wrote:
On 2014-07-24 17:26, Helmut Schaa wrote:
Introduce a new config symbol EXTRACT_DEBUGINFO to extract debuginfo
from all binaries. This depends on USE_STRIP and DEBUG.
The debuginfo of all packages will be extracted from the binary
and copied into "b
On 2014-07-24 17:26, Helmut Schaa wrote:
> Introduce a new config symbol EXTRACT_DEBUGINFO to extract debuginfo
> from all binaries. This depends on USE_STRIP and DEBUG.
>
> The debuginfo of all packages will be extracted from the binary
> and copied into "bin/$platform/debuginfo".
>
> This allow
Introduce a new config symbol EXTRACT_DEBUGINFO to extract debuginfo
from all binaries. This depends on USE_STRIP and DEBUG.
The debuginfo of all packages will be extracted from the binary
and copied into "bin/$platform/debuginfo".
This allows better debugging of coredumps by loading the debuginf
