Thanks David! On Tue, Mar 21, 2023 at 6:32 PM David Li <lidav...@apache.org> wrote:
> Not really, other than: > > * By searching the codebase for relevant strings. > * If you are building Arrow from source, you can use the option > ARROW_EXTRA_ERROR_CONTEXT [1] when configuring. This will get you a rough > stack trace (IIRC, if a function returns the status without using one of > the macros, it won't add a line to the trace). > > [1]: > https://github.com/apache/arrow/blob/1ba4425fab35d572132cb30eee6087a7dca89853/cpp/cmake_modules/DefineOptions.cmake#L608-L609 > > On Tue, Mar 21, 2023, at 18:12, Li Jin wrote: > > Hi, > > > > This might be a dumb question but when Arrow code raises an invalid > status, > > I observe that it usually pops up to the user without stack information. > I > > wonder if there are any tricks to show where the invalid status is coming > > from? > > > > Thanks, > > Li >
