[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mesa3d-dev
Subject:    Re: Degugging with gdb
From:       Manuel Dun <manueldun () gmail ! com>
Date:       2024-04-03 16:57:22
Message-ID: CADkQz_hdtDZ9vHt8Dk_OycEt-kCCJ3AoDA0QtMEeA4CxFw4dMw () mail ! gmail ! com
[Download RAW message or body]

Awesome, thanks for the info.

El mié, 3 abr 2024 a las 12:39, Adam Jackson (<ajax@redhat.com>) escribió:
> 
> I don't know anything about using Mesa as a meson subproject, but the way I usually \
> test a local Mesa build is: 
> https://docs.mesa3d.org/install.html#running-against-a-local-build-easy-way
> 
> For example if I wanted to run gdb on glxgears I might say:
> 
> $ meson devenv -C build gdb -q glxgears
> 
> You can also just say "meson devenv -C build" to get a subshell in the build \
> environment. Note that the initial working directory is set to the build dir, which \
> can be a little confusing if your command line includes relative paths, so don't \
> use relative paths if you can help it. 
> - ajax
> 
> On Sat, Mar 30, 2024 at 4:05 PM Manuel Dun <manueldun@gmail.com> wrote:
> > 
> > Hello
> > 
> > This is a continuation from a question I made in the mesa-user mailing list.
> > 
> > how would I set up mesa 3d to debug with gdb? and is it reasonable to do so?
> > 
> > I usually set libraries as meson subprojects but I don't know how to
> > get the meson dependency for mesa 3d.
> > 


[prev in list] [next in list] [prev in thread] [next in thread]