Hey,
Whenever wine crashes, I get a long stream of
err:dbghelp_stabs:stabs_parse Unknown stab type 0x2e err:dbghelp_stabs:stabs_parse Unknown stab type 0x4e err:dbghelp_stabs:stabs_parse Unknown stab type 0x2e err:dbghelp_stabs:stabs_parse Unknown stab type 0x4e err:dbghelp_stabs:stabs_parse Unknown stab type 0x2e err:dbghelp_stabs:stabs_parse Unknown stab type 0x4e err:dbghelp_stabs:stabs_parse Unknown stab type 0x2e err:dbghelp_stabs:stabs_parse Unknown stab type 0x4e
Does everyone else get that too? Does anyone have info on this? It's understandable to output an unknown type, but it does make the backtrace pretty much useless. After a couple parts of the bt, the error message files a couple hundred lines, then another couple lines of the bt, so I can't see the whole bt at once. Sometimes parts of the bt are scrolled up past my history limit. I don't mean to complain, but it is hampering debugging a bit.
James Hawkins a écrit :
Hey,
Whenever wine crashes, I get a long stream of
err:dbghelp_stabs:stabs_parse Unknown stab type 0x2e err:dbghelp_stabs:stabs_parse Unknown stab type 0x4e err:dbghelp_stabs:stabs_parse Unknown stab type 0x2e err:dbghelp_stabs:stabs_parse Unknown stab type 0x4e err:dbghelp_stabs:stabs_parse Unknown stab type 0x2e err:dbghelp_stabs:stabs_parse Unknown stab type 0x4e err:dbghelp_stabs:stabs_parse Unknown stab type 0x2e err:dbghelp_stabs:stabs_parse Unknown stab type 0x4e
Does everyone else get that too? Does anyone have info on this? It's understandable to output an unknown type, but it does make the backtrace pretty much useless. After a couple parts of the bt, the error message files a couple hundred lines, then another couple lines of the bt, so I can't see the whole bt at once. Sometimes parts of the bt are scrolled up past my history limit. I don't mean to complain, but it is hampering debugging a bit.
aren't using something generated on Darwin by any chance ? A+
On 5/14/05, Eric Pouech pouech-eric@wanadoo.fr wrote:
aren't using something generated on Darwin by any chance ? A+
Not that I know of. I'm running Fedora Core 4 test2. These errors crop up with a vanilla cvs, but I'll re-checkout everything and build again to see if the problem has gone away.
James Hawkins a écrit :
On 5/14/05, Eric Pouech pouech-eric@wanadoo.fr wrote:
aren't using something generated on Darwin by any chance ? A+
Not that I know of. I'm running Fedora Core 4 test2. These errors crop up with a vanilla cvs, but I'll re-checkout everything and build again to see if the problem has gone away.
I'm asking because those stabs types seem to be emitted only on darwin Anyway, that's easy to silence them since they're not documented in standard ELF format
On Saturday 14 May 2005 21:44, Eric Pouech wrote:
I'm asking because those stabs types seem to be emitted only on darwin Anyway, that's easy to silence them since they're not documented in standard ELF format
I have had this patch in my tree for a while now. Should I send it to wine-patches? Some googling turned up N_BNSYM for 0x2e and N_ENSYM for 0x4e. Does that ring a bell?
-Hans
Changelog: Silence some unknown stab type messages.
Hans Leidekker a écrit :
On Saturday 14 May 2005 21:44, Eric Pouech wrote:
I'm asking because those stabs types seem to be emitted only on darwin Anyway, that's easy to silence them since they're not documented in standard ELF format
I have had this patch in my tree for a while now. Should I send it to wine-patches? Some googling turned up N_BNSYM for 0x2e and N_ENSYM for 0x4e. Does that ring a bell?
but those seem only created for darwin from what I can see IMO, we should: - define the N_{BE}NSYM as any other stabs type - group them together in the case switch (they are paired anyway) - and add a comment to explain what it is
A+
[off] I love this title, it gets me every time.
It sounds like a tabloid newpaper headline. [/off]
On Sat, 14 May 2005 17:52:07 +0200, James Hawkins truiken@gmail.com wrote:
On 5/14/05, Eric Pouech pouech-eric@wanadoo.fr wrote:
aren't using something generated on Darwin by any chance ? A+
Not that I know of. I'm running Fedora Core 4 test2. These errors crop up with a vanilla cvs, but I'll re-checkout everything and build again to see if the problem has gone away.