PS>>Tried 20051013 and it worked :-)))
CGF> I'm sorry that it didn't occur to me much
CGF> earlier that this was a cygwin
CGF> heap problem that was fixed in a snapshot.
CGF> I guess that, as a rule of thumb,
CGF> "try a snapshot" is always a good idea.
Not to be a total brown nose, but I'v
On Fri, Oct 14, 2005 at 10:15:36AM -0700, Peter J. Stieber wrote:
>PS = Peter J. Stieber
>PS>>One last post before calling it a night. I built a debug
>PS>> version of the cygwin DLL as well and installed it.
>PS>> Here is the latest gdb session:
>
>CGF> I don't remember if I suggested trying a sna
PS = Peter J. Stieber
PS>>One last post before calling it a night. I built a debug
PS>> version of the cygwin DLL as well and installed it.
PS>> Here is the latest gdb session:
CGF> I don't remember if I suggested trying a snapshot
CGF> but I'm wondering if a snapshot would just fix
CGF> your pro
On Thu, Oct 13, 2005 at 11:50:45PM -0700, Peter J. Stieber wrote:
>One last post before calling it a night. I built a debug version of the
>cygwin DLL as well and installed it. Here is the latest gdb session:
I don't remember if I suggested trying a snapshot but I'm wondering if
a snapshot would
One last post before calling it a night. I built a debug version of the
cygwin DLL as well and installed it. Here is the latest gdb session:
Attaching to program `/bin/ld.exe', process 304
[Switching to thread 304.0x990]
(gdb) bt
#0 0x7c901231 in ntdll!DbgUiConnectToDbg ()
from /cygdrive/c/W
CGF> It is useless. You probaby have to continue
CGF> after ld has been attached to see where the
CGF> SEGV really is coming from.
Thanks. Here is the result...
GNU gdb 6.3.50_2004-12-28-cvs (cygwin-special)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU
OK. This time gdb seemed to attach to the broken ld process, but the
back trace still doesn't have symbols...
GNU gdb 6.3.50_2004-12-28-cvs (cygwin-special)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to chan
On Thu, Oct 13, 2005 at 10:33:46PM -0700, Peter J. Stieber wrote:
>1. I built the binutils code from the source.
>2. I renamed /usr/bin/ld.exe to /usr/bin/ld-old.exe.
>3. I copies ld-new.exe to /usr/bin.
>
>The debug session that starts when ld crashes repeats
>
>Program received signal SIGSEGV, Se
On Thu, Oct 13, 2005 at 09:35:06PM -0700, Peter J. Stieber wrote:
>PS = Pete Stieber
>PS>>> Do I also need to build a debug version of the cygwin DLL?
>
>BD = Brian Dessent
>BD>>It would help, since otherwise backtraces will only have raw
>BD>> addresses. Note that the cygwin configure script[*] ha
1. I built the binutils code from the source.
2. I renamed /usr/bin/ld.exe to /usr/bin/ld-old.exe.
3. I copies ld-new.exe to /usr/bin.
The debug session that starts when ld crashes repeats
Program received signal SIGSEGV, Segmentation fault.
over and over. It never seems to stop.
Was copying l
PS = Peter J. Stieber
PS>>> Sorry in advance for the stupid questions, but...
PS>>>
PS>>> I downloaded the binutils source package, and
PS>>> extracted the source. When
PS>>> I ran
PS>>>
PS>>> ./configure --help
PS>>>
PS>>> I didn't see a --enable-debug option or anything
PS>>> I though was equiva
PS = Pete Stieber
PS>>> Do I also need to build a debug version of the cygwin DLL?
BD = Brian Dessent
BD>>It would help, since otherwise backtraces will only have raw
BD>> addresses. Note that the cygwin configure script[*] has a
BD>> --enable-debugging switch, but this is for enabling lots of
BD
PS = Peter J. Stieber
PS>> Sorry in advance for the stupid questions, but...
PS>>
PS>> I downloaded the binutils source package, and
PS>> extracted the source. When
PS>> I ran
PS>>
PS>> ./configure --help
PS>>
PS>> I didn't see a --enable-debug option or anything
PS>> I though was equivalent. Am I
On Thu, Oct 13, 2005 at 04:39:13PM -0700, Brian Dessent wrote:
>"Peter J. Stieber" wrote:
>
>> Sorry in advance for the stupid questions, but...
>>
>> I downloaded the binutils source package, and extracted the source. When
>> I ran
>>
>> ./configure --help
>>
>> I didn't see a --enable-debug op
"Peter J. Stieber" wrote:
> Sorry in advance for the stupid questions, but...
>
> I downloaded the binutils source package, and extracted the source. When
> I ran
>
> ./configure --help
>
> I didn't see a --enable-debug option or anything I though was
> equivalent. Am I missing something?
Norm
PS = Peter J. Stieber on 10/9/2005 7:59 PM:
PS It's attached. I added the -t command to the g++ command so
PS the loader would list the files it was processing when it breaks.
PS The name of the object file in the last line should be
PS SimpleInterpolationTable.o, but it gets trunc
On Mon, Oct 10, 2005 at 11:18:06AM -0400, Christopher Faylor wrote:
>On Mon, Oct 10, 2005 at 06:13:15AM -0600, Eric Blake wrote:
>>-BEGIN PGP SIGNED MESSAGE-
>>Hash: SHA1
>>
>>According to Peter J. Stieber on 10/9/2005 7:59 PM:
>>> It's attached. I added the -t command to the g++ command so
On Mon, Oct 10, 2005 at 06:13:15AM -0600, Eric Blake wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>According to Peter J. Stieber on 10/9/2005 7:59 PM:
>> It's attached. I added the -t command to the g++ command so the loader
>> would list the files it was processing when it breaks. The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Peter J. Stieber on 10/9/2005 7:59 PM:
> It's attached. I added the -t command to the g++ command so the loader
> would list the files it was processing when it breaks. The name of the
> object file in the last line should be SimpleInterpo
Peter J. Stieber wrote:
[snip]
> Yes. I manually typed the g++ line in the attached output file. It broke
> as well.
>
> Thanks for trying to help René. Any other suggestions?
Nothing seems out of the ordinary.
Have you tried the obvious, roll back binutils to a previous version? Or any
other t
PS = Peter J. Stieber
PS>> I have a large simluation that I have built under cygwin for a
PS>> quite a while. Recently the ld phase of the build started
PS>> generating a stackdump (ld.exe.stackdump).
PS>>
PS>> Unfortunately I cannot recreate the problem with a simple
PS>> test case. I have attach
Peter J. Stieber wrote:
> I have a large simluation that I have built under cygwin for a quite a
> while. Recently the ld phase of the build started generating a stackdump
> (ld.exe.stackdump).
>
> Unfortunately I cannot recreate the problem with a simple test case. I
> have attached cygcheck out
22 matches
Mail list logo
