[ANNOUNCEMENT] Updated: binutils-20050610-1
I've made a new version of binutils available for installation. This version of binutils contains a fix which should stop the ld --auto-image-base option from locating dlls into the address space of the cygwin dll. For a brief description of this package, and a listing of the files it contains, see http://cygwin.com/packages/binutils . The project web page has more details: http://sourceware.org/binutils/ . To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at the above URL. Christopher Faylor -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: emacs won't run
On Fri, Dec 06, 2013 at 03:18:31PM +0100, marco atzeri wrote:
>Il 12/6/2013 2:38 PM, Andrea Venturoli ha scritto:
>> On 12/05/13 15:40, marco atzeri wrote:
>>
>>>> In the end I got a trace file (which is over 7MB!), but it's nothing I
>>>> can interpret.
>>>> What should I do?
>>>> Anything I should look for?
>>>
>>> any seriuos error ;-)
>>
>> Wish I could discern... :-)
>>
>
>the crash is here
>
>--- Process 3888, exception c005 at 610FA004
>[cut]
>--- Process 3888, exception c005 at 00597673
>--- Process 3888, exception c005 at 610D67B3
>
>
>$ addr2line.exe -a 610FA004 -e /usr/bin/cygwin1.dll
>0x610fa004
>/usr/src/debug/cygwin-1.7.26-1/winsup/cygwin/thread.cc:136
That is not a crash.
>but I do not see a clear reason of why it is happening
>
>verifyable_object_isvalid (void const *objectptr, thread_magic_t magic,
>void *static_ptr1,
>void *static_ptr2, void *static_ptr3)
>{
> myfault efault;
> if (efault.faulted (objectptr)) <<< here
> return INVALID_OBJECT; <<<
This is the return of "INVALID_OBJECT" if an invalid pointer is passed
to a thread routine.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: MinTTY "vs" rxvt (was Re: MinTTY 0.3.3)
On Sun, Jan 11, 2009 at 11:00:28PM -0500, Paul McFerrin wrote: > On Sun, Jan 11, 2009 at 03:22:14PM -0500, Charles Wilson wrote: >> Christopher Faylor wrote: Not sure what I'm doing here. >> Well, it's my main terminal. I tried MinTTY and I'm not sure yet whether >> it will supplant rxvt for my personal use, but it shows promise. >> > I've been using rxvt for years as my main terminal and just tried using > minTTY and really prefer not to use it. You see I'm and old man with poor > eye sight. The visual attributes of minTTY aren't the same that I use with > rxvt. The Lucida Console (white foreground on black) has less contrast as > the same font on rxvt. If I make it bold, it approaches nearly the same > brightness as rxvt but a little more blurry. These featurea don't go with > poor vision. > > I made the mistake of updating rxvt before and I learned no more updates, > please. Maybe it will help someone what options I use to make my > statements more clearer: >rxvt --backspacekey ^H -sbt 15 -fg white -bg black -geometry +75+80 -sr > -title "TTY$tty$label" -tn ansi -sl 3000 -fn 'Lucida Console-12' -e ksh & > My 2 cents worth, no more. You obviously have customized rxvt. I don't see why MinTTY would be any different. And, if you are not going to be updating rxvt it doesn't really matter what happens with the distribution since you wouldn't see it anyway. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
