Date: Sun, 21 Mar 2010 14:23:44 -0700 From: Garrett Cooper <yanefbsd@gmail.com> To: =?ISO-8859-1?B?Q2l2a2EsIEf8bnRlciAoTE5HLU1VRSk=?= <Guenter.Civka@lexisnexis.de> Cc: freebsd-current@freebsd.org, Andriy Gapon <avg@icyb.net.ua> Subject: Re: build failures after stdlib update Message-ID: <7d6fde3d1003211423p5c43161au12723f248d34de3f@mail.gmail.com> In-Reply-To: <permail-201003212111111e86ffa80000478a-a_best01@message-id.uni-muenster.de> References: <4BA6819E.4050504@icyb.net.ua> <permail-201003212111111e86ffa80000478a-a_best01@message-id.uni-muenster.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 21, 2010 at 2:11 PM, Alexander Best <alexbestms@wwu.de> wrote:
> Andriy Gapon schrieb am 2010-03-21:
>> on 21/03/2010 20:46 Alexander Best said the following:
>> > Andriy Gapon schrieb am 2010-03-21:
>> >> on 21/03/2010 14:53 Alexander Best said the following:
>> >>> *lol* sorry. ;)
>
>> >> No worries.
>> >> BTW, when that rash happens, are you able to examine the core with
>> >> gdb?
>> >> Is it possible to examine values of 's' and 'p' in strlen?
>
>> > 'p' is not available. i guess because the segfault happens before
>> > 'p' gets
>> > assigned.
>
>> > but mask01 = 0x101010101010101 and lp = (const long unsigned int *)
>> > 0xc092d8.
>
>> > but i'm not really familiar with gdb and debugging. so you might
>> > want to ask
>> > for certain commands. ;)
>
>> Not sure what I was dreaming of when I wrote my request.
>> I actually meant 'str' and 'lp'.
>
> *hehe* that makes more sense. well i already sent you lp. unfortunately str is
> not available to gdb:
>
> (gdb) print str
> Variable "str" is not available.
Sadly it may have been optimized out, which means that the best
way to resolve that little item is to compile with -O0 and
DEBUG_FLAGS=-g
HTH,
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d1003211423p5c43161au12723f248d34de3f>