On Thu, 12 Jul 2018 19:14:19 +0900 (JST)
YASUOKA Masahiko wrote:
>> On 2018/07/12 16:16, YASUOKA Masahiko wrote:
>>> > The next command of GDB does not work properly.
>>> > I use OpenBSD 6.3 and /usr/bin/gdb (GDB 6.3).
>>>
>>> It seems that gdb can't read the dwarf generated by clang properly.
On Thu, 12 Jul 2018 10:37:33 +0100
Stuart Henderson wrote:
> On 2018/07/12 16:16, YASUOKA Masahiko wrote:
>> > The next command of GDB does not work properly.
>> > I use OpenBSD 6.3 and /usr/bin/gdb (GDB 6.3).
>>
>> It seems that gdb can't read the dwarf generated by clang properly.
>> I found a
On 2018/07/12 16:16, YASUOKA Masahiko wrote:
> Hi,
>
> > The next command of GDB does not work properly.
> > I use OpenBSD 6.3 and /usr/bin/gdb (GDB 6.3).
>
> It seems that gdb can't read the dwarf generated by clang properly.
> I found a better fix at the upstream.
>
>
> https://sourceware.
Hi,
> The next command of GDB does not work properly.
> I use OpenBSD 6.3 and /usr/bin/gdb (GDB 6.3).
It seems that gdb can't read the dwarf generated by clang properly.
I found a better fix at the upstream.
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=ca5f395d6255337974262b
Hi tech,
I have a problem and I have ad hoc patch to solve this problem.
However, this patch is AD HOC. Does anybody have correct solution?
The next command of GDB does not work properly.
I use OpenBSD 6.3 and /usr/bin/gdb (GDB 6.3).
When I debuging my program with next command, I expect stop at
