Re: [Mono-dev] gdb and mono

2016-03-28 Thread David Evans 
Awesome, thank you! Looks like that is in mono 4.3.2.467 and 4.4.x, I’ll give 
it a try.

From: Zoltan Varga [mailto:var...@gmail.com]
Sent: Monday, March 28, 2016 12:39 PM
To: David Evans
Cc: mono-devel-list@lists.ximian.com
Subject: Re: [Mono-dev] gdb and mono

Hi,

  This was fixed some time ago by mono commit 
a6380f15f0db533e30870925e0125a859ab815cf.

Zoltan

On Mon, Mar 28, 2016 at 2:21 PM, David Evans 
<dev...@pacificbiosciences.com<mailto:dev...@pacificbiosciences.com>> wrote:
Sorry if this has been covered before, or is a current issue, but is there a 
way around these errors using gdb with mono 4.x?

I generally see “/build/buildd/gdb-7.7.1/gdb/dwarf2-frame.c:692: 
internal-error: Unknown CFI encountered.” whenever trying to look at things in 
gdb.

Thx!

(gdb) bt
#0  sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:85
#1  0x0061f977 in mono_sem_wait (sem=sem@entry=0x7fbacc000940, 
alertable=alertable@entry=0) at mono-semaphore.c:107
#2  0x0062465a in mono_thread_info_wait_for_resume (info=) at mono-threads.c:110
#3  mono_thread_info_end_self_suspend () at mono-threads.c:692
#4  0x005876dc in self_suspend_internal (thread=0x7fbadbb40430) at 
threads.c:4546
#5  mono_thread_execute_interruption (thread=thread@entry=0x7fbadbb40430) at 
threads.c:4050
#6  0x005879ac in mono_wait_uninterrupted 
(thread=thread@entry=0x7fbadbb40430, multiple=multiple@entry=0,
numhandles=numhandles@entry=1, handles=handles@entry=0x7fbad67fd638, 
waitall=waitall@entry=0, ms=ms@entry=1725, alertable=1)
at threads.c:1455
#7  0x00588f59 in 
ves_icall_System_Threading_WaitHandle_WaitOne_internal (this=, 
handle=0x100c, ms=1725,
exitContext=) at threads.c:1583
#8  0x40962760 in ?? ()
#9  0x0038 in ?? ()
#10 0x02521f28 in ?? ()
#11 0x06bd in ?? ()
#12 0x7fbada29f278 in ?? ()
#13 0x06bd in ?? ()
#14 0x7fbacc000e01 in ?? ()
#15 0x41641e7d in ?? ()
#16 0x7fbad67fd6f0 in ?? ()
#17 0x7fbad67fd660 in ?? ()
/build/buildd/gdb-7.7.1/gdb/dwarf2-frame.c:692: internal-error: Unknown CFI 
encountered.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n
/build/buildd/gdb-7.7.1/gdb/dwarf2-frame.c:692: internal-error: Unknown CFI 
encountered.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
Command aborted.


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com<mailto:Mono-devel-list@lists.ximian.com>
http://lists.ximian.com/mailman/listinfo/mono-devel-list

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] gdb and mono

2016-03-28 Thread Zoltan Varga 
Hi,

  This was fixed some time ago by mono commit
a6380f15f0db533e30870925e0125a859ab815cf.

Zoltan

On Mon, Mar 28, 2016 at 2:21 PM, David Evans 
wrote:

> Sorry if this has been covered before, or is a current issue, but is there
> a way around these errors using gdb with mono 4.x?
>
>
>
> I generally see “/build/buildd/gdb-7.7.1/gdb/dwarf2-frame.c:692:
> internal-error: Unknown CFI encountered.” whenever trying to look at
> things in gdb.
>
>
>
> Thx!
>
>
>
> (gdb) bt
>
> #0  sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:85
>
> #1  0x0061f977 in mono_sem_wait (sem=sem@entry=0x7fbacc000940,
> alertable=alertable@entry=0) at mono-semaphore.c:107
>
> #2  0x0062465a in mono_thread_info_wait_for_resume
> (info=) at mono-threads.c:110
>
> #3  mono_thread_info_end_self_suspend () at mono-threads.c:692
>
> #4  0x005876dc in self_suspend_internal (thread=0x7fbadbb40430) at
> threads.c:4546
>
> #5  mono_thread_execute_interruption (thread=thread@entry=0x7fbadbb40430)
> at threads.c:4050
>
> #6  0x005879ac in mono_wait_uninterrupted 
> (thread=thread@entry=0x7fbadbb40430,
> multiple=multiple@entry=0,
>
> numhandles=numhandles@entry=1, handles=handles@entry=0x7fbad67fd638,
> waitall=waitall@entry=0, ms=ms@entry=1725, alertable=1)
>
> at threads.c:1455
>
> #7  0x00588f59 in
> ves_icall_System_Threading_WaitHandle_WaitOne_internal (this= out>, handle=0x100c, ms=1725,
>
> exitContext=) at threads.c:1583
>
> #8  0x40962760 in ?? ()
>
> #9  0x0038 in ?? ()
>
> #10 0x02521f28 in ?? ()
>
> #11 0x06bd in ?? ()
>
> #12 0x7fbada29f278 in ?? ()
>
> #13 0x06bd in ?? ()
>
> #14 0x7fbacc000e01 in ?? ()
>
> #15 0x41641e7d in ?? ()
>
> #16 0x7fbad67fd6f0 in ?? ()
>
> #17 0x7fbad67fd660 in ?? ()
>
> /build/buildd/gdb-7.7.1/gdb/dwarf2-frame.c:692: internal-error: Unknown
> CFI encountered.
>
> A problem internal to GDB has been detected,
>
> further debugging may prove unreliable.
>
> Quit this debugging session? (y or n) n
>
> /build/buildd/gdb-7.7.1/gdb/dwarf2-frame.c:692: internal-error: Unknown
> CFI encountered.
>
> A problem internal to GDB has been detected,
>
> further debugging may prove unreliable.
>
> Create a core file of GDB? (y or n) n
>
> Command aborted.
>
>
>
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

[Mono-dev] gdb and mono

2016-03-28 Thread David Evans 
Sorry if this has been covered before, or is a current issue, but is there a 
way around these errors using gdb with mono 4.x?

I generally see "/build/buildd/gdb-7.7.1/gdb/dwarf2-frame.c:692: 
internal-error: Unknown CFI encountered." whenever trying to look at things in 
gdb.

Thx!

(gdb) bt
#0  sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:85
#1  0x0061f977 in mono_sem_wait (sem=sem@entry=0x7fbacc000940, 
alertable=alertable@entry=0) at mono-semaphore.c:107
#2  0x0062465a in mono_thread_info_wait_for_resume (info=) at mono-threads.c:110
#3  mono_thread_info_end_self_suspend () at mono-threads.c:692
#4  0x005876dc in self_suspend_internal (thread=0x7fbadbb40430) at 
threads.c:4546
#5  mono_thread_execute_interruption (thread=thread@entry=0x7fbadbb40430) at 
threads.c:4050
#6  0x005879ac in mono_wait_uninterrupted 
(thread=thread@entry=0x7fbadbb40430, multiple=multiple@entry=0,
numhandles=numhandles@entry=1, handles=handles@entry=0x7fbad67fd638, 
waitall=waitall@entry=0, ms=ms@entry=1725, alertable=1)
at threads.c:1455
#7  0x00588f59 in 
ves_icall_System_Threading_WaitHandle_WaitOne_internal (this=, 
handle=0x100c, ms=1725,
exitContext=) at threads.c:1583
#8  0x40962760 in ?? ()
#9  0x0038 in ?? ()
#10 0x02521f28 in ?? ()
#11 0x06bd in ?? ()
#12 0x7fbada29f278 in ?? ()
#13 0x06bd in ?? ()
#14 0x7fbacc000e01 in ?? ()
#15 0x41641e7d in ?? ()
#16 0x7fbad67fd6f0 in ?? ()
#17 0x7fbad67fd660 in ?? ()
/build/buildd/gdb-7.7.1/gdb/dwarf2-frame.c:692: internal-error: Unknown CFI 
encountered.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n
/build/buildd/gdb-7.7.1/gdb/dwarf2-frame.c:692: internal-error: Unknown CFI 
encountered.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
Command aborted.

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list